agentleFS
Sign inStart free
pavelzbornikpavelzbornik/whisperX-FastAPI/.claude/skills/pr-ready/SKILL.md

pr-ready

Skill188 starsChanged 7 months agoMITArchived repositoryView on GitHub

Validate code quality, run tests, check coverage, and create a PR when all checks pass. Use when ready to submit work.

  • Commits and pushes

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Lint and format: Run task check (ruff check + ruff format + mypy).

    line 13
  2. Very specific:

    Run tests: Run task test (full suite with ≥80% coverage gate).

    line 14
  3. Very specific:

    Coverage on new code: Run uv run pytest --cov=app --cov-report=term-missing and check that files changed on this branch have >80% coverage.

    line 15
  4. Very specific:

    Review diff: Run git diff $(git merge-base HEAD dev)...HEAD --stat to summarize changes.

    line 16
  5. Very specific:

    Create PR: Only when steps 1-4 pass, commit any remaining changes and create the PR with gh pr create targeting dev.

    line 17
  6. Distinctive:

    If any step fails, fix the issue and re-run that step before proceeding.

    line 19

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

Prepare and validate a pull request. Only create the PR when all checks pass.

Steps

  1. Lint and format: Run task check (ruff check + ruff format + mypy). Fix any issues found.
  2. Run tests: Run task test (full suite with ≥80% coverage gate). If tests fail, diagnose and fix.
  3. Coverage on new code: Run uv run pytest --cov=app --cov-report=term-missing and check that files changed on this branch have >80% coverage. If not, write tests for uncovered paths.
  4. Review diff: Run git diff $(git merge-base HEAD dev)...HEAD --stat to summarize changes. Flag anything that looks unintentional.
  5. Create PR: Only when steps 1-4 pass, commit any remaining changes and create the PR with gh pr create targeting dev. Include a structured description with summary, test plan, and coverage delta.

If any step fails, fix the issue and re-run that step before proceeding. Do not create the PR until everything is green.

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