fix-precommit

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 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.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Run the pre-commit hooks and fix any errors they report.

   line 6
2. Very specific:

   Run uv run pre-commit run --all-files and capture the output.

   line 9
3. Distinctive:

   Read the output carefully.

   line 10
4. Very specific:

   After fixing all issues, re-run uv run pre-commit run --all-files to verify all hooks pass.

   line 15
5. Distinctive:

   If new errors appear in the re-run, repeat the fix-and-verify cycle until the run is fully clean.

   line 16
6. Distinctive:

   Follow the project style: single quotes for string literals, double quotes only for docstrings.

   line 19
7. Distinctive:

   Do not add unnecessary changes beyond what the hooks require.

   line 20
8. Distinctive:

   Do not commit anything.

   line 21

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