agentleFS
Sign inStart free
jrjsmrtnjrjsmrtn/project-orchestration-skills/skills/setup-pre-commit/SKILL.md

setup-pre-commit

Skill17 starsChanged 10 days agoMITView on GitHub

DEPRECATED — renamed to setup-git-hooks in 0.1.29. This skill should be used only to redirect; invoke setup-git-hooks instead for configuring two-stage git hooks (pre-commit + pre-push) with either pre-commit or lefthook.

124 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use migrate-to-shoehorn, writing-beats and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 73 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 63 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 41 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 63 projects that use this

  • simo97Skill

    edit-article

    The user will invoke this skill to help them edit an article.

    Also in 38 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 52 projects that use this

  • +3 more from simo97
  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 112 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not follow any procedure from this file.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 112 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup Pre-commit Hooks (deprecated)

This skill was renamed to setup-git-hooks in 0.1.29. Invoke that instead.

Do not follow any procedure from this file. It retains no content — it exists solely so that an invocation of the old name yields a pointer rather than silence.

Why it was renamed

The old name was wrong on two axes at once:

  • It named one of the two stages. The skill's thesis is the two-stage split — fast checks on commit, thorough checks on push. The pre-push stage is roughly a third of the content and carries the checks that catch the expensive defects.
  • It named one of the two supported hook managers. The skill documents both pre-commit and lefthook; its "Install Hook Framework" step mentions lefthook more often than pre-commit, and roughly half the skill (.editorconfig, secret-detection architecture, .gitignore hardening, multi-remote protection) involves no hook manager at all.

The practical effect was that maintainers on Elixir, Go or Rust projects read "pre-commit", correctly inferred "that is the Python hook framework", and never reached the content that had nothing to do with it.

See workspace ADR-0013.

Migration

Replace any invocation of setup-pre-commit with setup-git-hooks. There is no behavioural change — same workflow, same steps, same outputs.

Removal

This stub will be removed at 0.2.0. It exists only for the deprecation window, because the skill, plugin and marketplace manifests provide no rename, alias or redirect mechanism — content-level deprecation is the only graceful path the format offers.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free