agentleFS
Sign inStart free
5uck1ess5uck1ess/devkit/skills/pr-ready/SKILL.md

pr-ready

Skill4 starsChanged 4 months agoMITView on GitHub

Full end-to-end PR pipeline — validate → necessity-check → lint (loop) → test (loop) → security scan → doc-check → changelog → create-pr → monitor reviews (loop). Takes a branch from "code done" to "merged" with every gate enforced. Use when the user asks to "submit a PR", "open a pull request", "ship this", "make this PR-ready", "finalize this branch", or wants the full pipeline run end-to-end with CI monitoring and reviewer-comment handling automated. Worth the ceremony when: lint and test gates must pass before the PR opens, docs need syncing alongside code (README, ROADMAP, SKILL.md, workflows), security scan is required, or the user wants reviewer comments automatically classified and responded to. Do NOT use for a quick commit+push+PR without gates — use `/commit-commands:commit-push-pr` for that lighter path. Do NOT use when already mid-PR and just handling existing review comments in isolation. Do NOT use on the main branch or with uncommitted changes — the validate step will block you. This is devkit's heaviest PR workflow; pick it when you want everything run.

  • Commits and pushes

12 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

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    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. Very specific:

    Start the workflow via the devkit engine:

    line 28
  2. Very specific:

    Use the devkit_start tool with workflow: "pr-ready" and input: "{input}".

    line 30
  3. Distinctive:

    Never dismiss reviews — only re-request after fixing

    line 49
  4. Distinctive:

    Stop after 10 monitor iterations or when stuck (3 iters with zero progress)

    line 52

“Common” is measured: kept by at least 6 in 10 of the 12 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

PR Ready

Deterministic PR pipeline: validate → necessity → lint (loop) → test (loop) → security → doc-check → changelog → create PR → monitor (loop).

Invoke

Start the workflow via the devkit engine:

Use the devkit_start tool with workflow: "pr-ready" and input: "{input}".

Then follow each step the engine returns. Call devkit_advance after completing each step. The engine controls step order, gates, and loops. Do NOT skip steps.

What it does

  1. validate — checks not on main, no uncommitted changes, commits ahead of main
  2. necessity — removes debug prints, unrelated changes, stray files from the diff
  3. lint — runs linter, fixes violations, loops until clean
  4. test — runs test suite, fixes failures, loops until passing
  5. security — scans for hardcoded secrets, injection, XSS, traversal, insecure deps
  6. doc-check — classifies the diff (feature/bugfix/breaking/internal/docs-only) and decides per-file whether README, ROADMAP, CLAUDE.md, skills/*/SKILL.md, plugin.json, or workflows/*.yml need updates. Applies mechanical edits directly (moving roadmap bullets, adding command rows, syncing SKILL.md step lists); flags ambiguous updates as [!] in the output checklist. Commits applied edits with docs: update ... so they land in the PR alongside the code. CHANGELOG.md is intentionally skipped — it is managed by the release pipeline. Runs before changelog so any doc commit it creates is captured in the PR description.
  7. changelog — generates entry from git diff (now includes any doc-check commits)
  8. create-pr — pushes branch, creates PR via gh pr create with title/summary/changelog/test plan
  9. monitor — waits for CI, classifies reviewer comments (code_fix/style_nit/question/false_positive/out_of_scope), applies fixes, replies, pushes, loops until all resolved

Rules

  • Never force-push
  • Never dismiss reviews — only re-request after fixing
  • Reply to false positives with evidence, not dismissal
  • Escalate architectural changes via AskUserQuestion
  • Stop after 10 monitor iterations or when stuck (3 iters with zero progress)

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.

Check your setup, free