agentleFS
raffaelefarinaroraffaelefarinaro/ciaobot/skills/pr/SKILL.md

pr

Skill11 starsChanged 10 days agoApache-2.0View on GitHub

Pre-PR quality gate — run /code-review --fix on the branch diff before opening or updating a pull request. Trigger on "open a PR", "create a pull request", "ready for review", "/pr", or when about to push a branch for review.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before opening or updating a pull request, run this gate.

    line 10
  2. Distinctive:

    Inspect: Read the applied edits with git diff.

    line 15
  3. Very specific:

    Open or update the PR: only after step 2 (gh pr create / push / update).

    line 16
  4. Very specific:

    Only skip /code-review if it is genuinely absent from the environment (check with the Skill tool / /help) — say so explicitly and do the …

    line 23

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

PR quality gate

Contributor/project skill — lives in the repo's workspace skills/ folder, not ciao/stock/skills/. It is for people working on Ciaobot and is deliberately not packaged or shipped to end-user installs. ciao sync-skills mirrors it into the runtime-discovered .claude/skills/ catalog. Don't move it into ciao/stock/.

Before opening or updating a pull request, run this gate. Do not open the PR until findings are applied or explicitly deferred with the user.

Steps

  1. Review + apply. Invoke /code-review --fix on the branch diff (commits ahead of upstream plus uncommitted changes). Pass a higher effort for large or risky diffs. If the diff touches auth, secrets, or external input, run security-review instead (or in addition).
  2. Inspect. Read the applied edits with git diff. Keep, amend, or discard (git add -p / git checkout -- .) before committing anything the review wrote.
  3. Open or update the PR only after step 2 (gh pr create / push / update).

Optional after the PR exists: /code-review --comment posts findings as inline PR comments.

Notes

  • /code-review already covers reuse, simplification, and efficiency findings. Do not also require /simplify unless you specifically want a cleanup-only autofix without a bug hunt.
  • Only skip /code-review if it is genuinely absent from the environment (check with the Skill tool / /help) — say so explicitly and do the equivalent review by hand.
  • Release cuts use the same gate on a wider range; see skills/ciao-release/SKILL.md.

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.