agentleFS
nwiizonwiizo/ccswarm/.agents/skills/review-fix/SKILL.md

review-fix

Skill156 starsChanged 11 days agoMITView on GitHub

Review the requested diff, fix clear correctness issues, and verify the affected behavior.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

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

    Read the changed code, callers, and applicable project rules.

    line 10
  2. Distinctive:

    Run this workflow in the current session unless delegation is explicitly requested.

    line 29

“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

Review staged, unstaged, and relevant untracked changes unless the user selects a narrower diff. Inspect git status --short and git diff HEAD; if there is nothing to review, report that and stop.

Read the changed code, callers, and applicable project rules. Prioritize bugs, security issues, broken references, ignored CLI options, provider capability mismatches, and violations of the workflow/session/provider boundaries in AGENTS.md. Use nwiizo-coding-style for Rust structure and duplication analysis; similarity scores alone do not justify a refactor.

Establish relevant baseline checks when needed to distinguish existing failures from regressions. Fix clear issues within the requested scope with minimal changes. Report design choices and unrelated failures without expanding the assignment. Preserve other contributors' edits; if a fix fails verification, correct it or undo only that fix and report the unresolved finding.

For Rust changes, run the required workspace checks in AGENTS.md, including tests of affected behavior. For configuration and documentation, validate syntax, referenced paths, and the affected tool's loading behavior. Reuse passing checks while their inputs remain unchanged.

Report fixed issues, remaining findings with file references, and verification results. Distinguish pre-existing failures from failures caused by the change. Run this workflow in the current session unless delegation is explicitly requested.

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.