We split this skill into the rules it gives an agent

11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈6

  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
• could be automatic: a setting could enforce it

1. Very specific:

   Read loop-constraints.md from the project root.

   line 13
2. Very specific:

   Check if loop-pause-all is active → exit immediately.

   line 15
3. Distinctive:

   Before pushing: re-read the Push & Merge section.

   line 20
4. Distinctive:

   Before editing a file: re-read the Paths section.

   line 21
5. Distinctive:

   Before proposing a fix: re-read the Code section.

   line 22
6. Distinctive:

   Before merging: re-read the Push & Merge section.

   line 23
7. Distinctive:

   Always begin with a one-line confirmation:

   line 27
8. Very specific:

   If no loop-constraints.md exists, say so and proceed with default safety rules from docs/safety.md.

   line 33
9. Very specific:

   If loop-constraints.md is absent, enforce these minimums:

   line 44
10. Very specific:

    Never edit .env, .env.*, auth/, payments/, secrets/, credentials/

    line 45
11. Distinctive:

    Never auto-merge to maincould be automatic

    line 46

≈ “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.