agentleFS
ArchitektApxArchitektApx/cursor-skills-for-claude/skills/review-and-ship/SKILL.md

review-and-ship

Skill0 starsChanged 15 days agoMITView on GitHub

Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

6 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 4

    Common

    Most of the 3 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. Common:

    Run targeted tests for changed behavior.

    line 15
  2. Common:

    Commit selective files with a concise message.

    line 18
  3. Common:

    Keep commits focused and avoid unrelated file changes.

    line 33
  4. Common:

    If pre-commit checks fail, fix the issues rather than bypassing hooks.

    line 34
  5. Very specific:

    Use gh pr checks instead of GitHub Actions-only commands when judging PR readiness.

    line 35

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

Review and ship

Trigger

Reviewing changes before shipping. Close key issues, verify behavior, and open or update a PR.

Workflow

  1. Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent relevant chats if useful.
  2. Run targeted tests for changed behavior. If no focused tests exist, decide whether to add them or document the gap.
  3. Review for correctness, regressions, security, and intent fit. Use parallel subagents for larger diffs.
  4. Fix critical issues before finalizing and re-run affected tests.
  5. Commit selective files with a concise message.
  6. Push branch and open or update a PR.

Suggested Checks

git fetch origin main
git diff origin/main...HEAD
git status
gh pr checks --json name,bucket,state,workflow,link

Guardrails

  • Prioritize correctness, security, and regressions over style-only comments.
  • Keep commits focused and avoid unrelated file changes.
  • If pre-commit checks fail, fix the issues rather than bypassing hooks.
  • Use gh pr checks instead of GitHub Actions-only commands when judging PR readiness.

Output

  • Findings summary (critical, warning, note)
  • Tests run and outcomes
  • PR URL

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.