agentleFS
salvo8519salvo8519/fairmark/.claude/skills/pre-pr/SKILL.md

pre-pr

Skill1 starsChanged 2 days agoApache-2.0View on GitHub

Run the full local quality gate and both review subagents, then draft the pull request description. Use before pushing a branch or opening a PR.

10 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check git diff main...HEAD -- tests/golden: if an existing expected value changed, the PR needs the numerical-change label and maintainer …

    line 16

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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
<!-- Generated from .agents/skills/pre-pr/SKILL.md by scripts/sync_agents.py. Edit the source, not this file. -->
  1. uv run just check — must be green. Fix and re-run until it is.
  2. Classify the pull request by tier ("Effort proportional to risk" in AGENTS.md):
    • Small: read the diff yourself; no review subagent.
    • Substantial: run the code-reviewer subagent once on the branch diff. Fix every finding and check each fix against the list; a second pass only for a blocking logic defect.
    • Numerical change: as substantial, plus numerical-auditor. Fix discrepancies.
  3. The numerical audit of main is scheduled (weekly and at milestone end); do not run it for pull requests outside the numerical-change tier.
  4. Check git diff main...HEAD -- tests/golden: if an existing expected value changed, the PR needs the numerical-change label and maintainer approval — say so explicitly.
  5. Draft the PR:
    • Title: Conventional Commit, citing the spec (feat(dcf): … [SPEC-0001]).
    • Body: summary, requirements/AC covered, tests added, docs updated, reviewer verdicts, the PR template checklist ticked honestly.

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.