agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/address-feedback/SKILL.md

address-feedback

Skill1 starsChanged 41 days agoMITView on GitHub

Resolve PR review and bot feedback efficiently. Use when responding to review comments, Copilot/Bugbot notes, or requested changes.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security and git-workflow.

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.
  • 0xSeroSkill

    security

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    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:

    Do not ignore actionable correctness/security comments.

    line 19
  2. Distinctive:

    Do not expand scope into unrelated refactors while addressing feedback.

    line 20
  3. Distinctive:

    Prefer one commit or a clear commit series for review responses when repo style allows.

    line 21
  4. Distinctive:

    If feedback conflicts with requirements, ask the user before implementing.

    line 22

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

Address Feedback

Process

  1. Collect all review threads and CI/bot comments.
  2. Deduplicate; group by file/theme.
  3. Classify each: must-fix, nice-to-have, disagree/needs discussion.
  4. Fix must-fix with minimal diffs; run relevant checks.
  5. Reply to threads with what changed or why not.
  6. Re-request review when blockers are cleared.

Rules

  • Do not ignore actionable correctness/security comments.
  • Do not expand scope into unrelated refactors while addressing feedback.
  • Prefer one commit or a clear commit series for review responses when repo style allows.
  • If feedback conflicts with requirements, ask the user before implementing.

Output

Fixed:
- thread/file — change
Deferred:
- ... — reason
Questions:
- ...

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