agentleFS
fboulnoisfboulnois/skills/review-branch/SKILL.md

review-branch

Skill1 starsChanged 6 days agoMITView on GitHub

Reviews a branch for code and security issues, verifies findings, and reports high and medium severity issues in a fenced markdown block. Use when asked to review a branch.

8 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

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure the description is less than 400 characters

    line 16
  2. Distinctive:

    If there are no medium or high findings, say so instead of printing an empty block.

    line 17
  3. Distinctive:

    After the block, list low findings as one short bullet each, then one line with the security review result.

    line 19

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

/code-review and /security-review the mentioned branch. Verify all findings before presenting them.

Output

Put all medium and high findings, high first, in a single fenced markdown code block so the raw markdown can be copied. Inside the block, each finding is exactly one line in this format, separated by a blank line, with nothing else in the block (no headings, no notes):

<n>. [<High|Medium>] <finding>: <file:line> <description>

  • Ensure the description is less than 400 characters
  • If there are no medium or high findings, say so instead of printing an empty block.

After the block, list low findings as one short bullet each, then one line with the security review result.

Example

**1. [Medium] Skip cutoff is dated from the wrong event:** `docs/plan.md:180` The cutoff uses the first `true` in prod, but ...

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.