agentleFS
System-Error-WorldwideSystem-Error-Worldwide/the-loop/.agents/skills/pre-commit-review/SKILL.md

pre-commit-review

Skill0 starsChanged 3 months agoMITView on GitHub

Static check gate before risky write operations.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Use before committing or applying multi-file write batches.

    line 17
  2. Distinctive:

    Stop with a precise error for missing authority, expired lease, namespace mismatch, unsafe proof, private data exposure, unknown …

    line 40

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

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

Pre-Commit Review

Static check gate before risky write operations.

Use when

  • Use before committing or applying multi-file write batches.

Inputs

  • Active run, objective, track, and authority context.
  • Declared track boundaries and budget controls.
  • Typed evidence references and required file paths.

Procedure

  1. Validate changed files against project-owned schema and boundary checks.
  2. Fail closed on missing allowlist, drift, private secret, or unverified dependency changes.
  3. Emit explicit required fixes before write acceptance.
  4. Allow no write when evidence is incomplete.
  5. Return audit-style report with precise remediation paths.

Output contract

  • Deterministic status, evidence hash list, and explicit status transitions.
  • Typed halt reason with exact next-step obligations when blocked.

Halt conditions

Stop with a precise error for missing authority, expired lease, namespace mismatch, unsafe proof, private data exposure, unknown capability, or unverified behavior claim.

Notes

Core execution does not require network access or the source checkout. Use the bundled fallback behavior when live capabilities are blocked.

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.