We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈11

  Distinctive · estimate

  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 finish a review until the review is actually useful.

   line 8
2. Distinctive:

   Verify that the change addresses the stated problem and does not create a hidden scope expansion.

   line 12
3. Distinctive:

   Check correctness, maintainability, operability, and security risk.

   line 13
4. Distinctive:

   Leave actionable feedback with a clear recommendation.

   line 19
5. Distinctive:

   If a change is not ready, say so clearly and explain why.

   line 21
6. Distinctive:

   If a change is ready, explain the reason concisely and specifically.

   line 22
7. Distinctive:

   Do not approve a change just because it is "probably fine."

   line 26
8. Distinctive:

   Do not leave vague feedback such as "needs work" without explaining the problem.

   line 27
9. Distinctive:

   Do not let style concerns override correctness and risk.

   line 28
10. Distinctive:

    Do not treat review as a formality when the change has real impact.

    line 29
11. Distinctive:

    Use this skill to ensure reviews improve the system rather than merely adding delay.

    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.