flag-review-finding
Skill2 starsChanged 18 days agoMITView on GitHub
Add, list, edit, or resolve a structured code-review improvement flag. Use it when the user says a review finding was wrong, noisy, or missed something and wants that recorded.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audit-repositorySkill
- change-skillSkill
- evaluate-skillSkill
- implement-changeSkill
- review-repositorySkill
- runtime-canarySkill
- shepherd-pull-requestsSkill
- audit-repositorySkill
- change-skillSkill
- evaluate-skillSkill
- implement-changeSkill
- review-repositorySkill
- runtime-canarySkill
- shepherd-pull-requestsSkill
- audit-ai-configSkill
- audit-skillSkill
- curate-agent-memorySkill
- dotnet-dependenciesSkill
- dotnet-formatSkill
- ejryan89-code-review-coreSkill
- ejryan89-skill-coreSkill
- github-activity-reportSkill
- repo-cleanupSkill
- review-documentSkill
- review-insightsSkill
- review-prsSkill
- update-coding-agent-skillsSkill
- update-pr-dashboardSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 40
Leave out the option for a value that stays.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flag a review finding
Use the configured code-review flag store through the commands below; do not edit the store, a Markdown ledger, or a review report. Each command prints one fact per line. A failure prints FAILED <reason> and changes nothing; show the reason. Keep each command's form: -- before the free-text values and = joining --category and --body to theirs let a value begin with -.
Add a flag with a category and rationale. Associate it with a pull request and finding when it concerns one, using the full owner/repo identity and the finding's label, such as v2 F002, as the review report shows it. When neither the user nor the conversation gives the label, list the pull request's open findings and ask the user which one they mean:
{{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/flag_review_finding.py" findings --repository "<owner/repo>" --pull "<number>"It prints FINDING v<version> <finding> <severity> <path>:<line> <headline> per open or unverified finding, under the label its report shows, then COUNT <n>. Then add the flag with the label as written; it refuses a finding that review does not have:
{{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/flag_review_finding.py" add --repository "<owner/repo>" --pull "<number>" --finding "<label>" -- "<category>" "<rationale>"Without a finding, leave out the options before --. It prints ADDED <flag id>. review-insights links a flag that names a finding to the recommendations covering it, and its synthesis can name any open flag, one that names no finding included; accepting a recommendation resolves the flags it links.
List the open flags:
{{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/flag_review_finding.py" listIt prints FLAG <flag id> <category> <target> <body> per open flag, with the body cut to 160 characters and - as the target of a flag that names neither a repository nor a pull request, then COUNT <n>.
Correct an open flag's category, rationale, or both by its ID; what it names and its status stay as they are:
{{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/flag_review_finding.py" edit "<flag id>" --category="<category>" --body="<rationale>"Leave out the option for a value that stays. It prints EDITED <flag id>, and refuses a resolved or unknown flag.
Resolve an open flag by its ID (such as RF-000004) with a non-empty resolution:
{{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/flag_review_finding.py" resolve -- "<flag id>" "<resolution>"It prints RESOLVED <flag id>, or ALREADY_RESOLVED <flag id> when the flag was resolved earlier; it keeps that earlier resolution.
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
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.

