We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  Distinctive · estimate

  This author's own choices. Worth a look.

• 5

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use this wrapper only after the explicit opt-in described in the frontmatter.

   line 8
2. Very specific:

   Use this skill to run $commit in approval-first mode, defaulting to the whole working tree.

   line 10
3. Very specific:

   Before starting, load and follow $commit.

   line 12
4. Very specific:

   When using $commit, force plan mode:

   line 24
5. Distinctive:

   If the user names a subset or asks for only the current agent's changes, honor that narrower scope.

   line 27
6. Very specific:

   Always present a commit plan first and wait for explicit approval such as go.

   line 28
7. Distinctive:

   Do not stage or commit before approval, even if there is only one logical commit.

   line 29
8. Distinctive:

   After approval, create all agreed commits without asking again unless the working tree changes unexpectedly.

   line 30
9. Very specific:

   Treat go after a previously presented plan as approval for that plan, then re-check the working tree before staging.

   line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.