agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/address-github-pr-comments/SKILL.md

address-github-pr-comments

Skill9 starsChanged 3 months agoMITView on GitHub

Address review comments on the current GitHub PR

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Run relevant tests or linters after impactful changes

    line 23
  2. Distinctive:

    Do not dismiss valid security feedback.

    line 41
  3. Distinctive:

    Do not commit, push, merge, or run production scripts without consent.

    line 43
  4. Distinctive:

    Do not print, log, or commit secrets or credentials.

    line 44

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Process outstanding reviewer feedback, apply required fixes, and draft clear responses for each GitHub pull-request comment.

Steps

  1. Sync and audit comments
    • Pull the latest branch changes
    • Open the PR conversation view and read every unresolved comment
    • Group comments by affected files or themes
  2. Plan resolutions
    • List the requested code edits for each thread
    • Identify clarifications or additional context you must provide
    • Note any dependencies or blockers before implementing changes
  3. Implement fixes
    • Apply targeted updates addressing one comment thread at a time
    • Run relevant tests or linters after impactful changes
    • Stage changes with commits that reference the addressed feedback
  4. Draft responses
    • Summarize the action taken or reasoning provided for each comment
    • Link to commits or lines when clarification helps reviewers verify
    • Highlight any remaining questions or follow-up needs

Response Checklist

  • All reviewer comments acknowledged
  • Required code changes implemented and tested
  • Clarifying explanations prepared for nuanced threads
  • Follow-up items documented or escalated
  • PR status updated for reviewers

Guardrails

  • Push only when the user asks; do not push review fixes unrequested.
  • Do not dismiss valid security feedback; address it or justify with evidence first.
  • Address one comment thread at a time and run tests after impactful changes.
  • Do not commit, push, merge, or run production scripts without consent; wait for an explicit request before any destructive git action.
  • Do not print, log, or commit secrets or credentials; flag any exposed secret instead of including it in a commit or comment.

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