agentleFS
Sign inStart free
spiriMirrorspiriMirror/libuipc/.cursor/skills/fix-pr/SKILL.md

fix-pr

Skill351 starsChanged 3 months agoApache-2.0View on GitHub

Fix a pull request based on review feedback

  • Deletes or force-pushes

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use rebase, deslop and 1 more.

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.
  • raineSkill

    rebase

    Rebase the current branch with smart conflict resolution.

    Also in 3 projects that use this

  • SentrySkill

    deslop

    Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no PR number is provided, list and ask the developer to pick:

    line 15
  2. Very specific:

    Note: Always use --repo spiriMirror/libuipc to reference the upstream repository (works with forks).

    line 21
  3. Distinctive:

    Follow the owner working agreements.

    line 25
  4. Very specific:

    If the output is too long, store it in a temporary file for reference (output/ is gitignored):

    line 35
  5. Distinctive:

    Check the PR status, if there is a conflict, you need to resolve it first:

    line 44
  6. Distinctive:

    Follow the same test procedure as fix-issue step 4:

    line 58
  7. Distinctive:

    Run relevant tests to verify the fix.

    line 60
  8. Distinctive:

    Add new tests if the feedback requires new coverage.

    line 61
  9. Distinctive:

    Use the commit command to format, commit, and push.

    line 66

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

Fix PR

Overview

Fix a pull request based on review feedback comments.

1. Identify the PR

If no PR number is provided, list and ask the developer to pick:

gh pr list --repo spiriMirror/libuipc

Note: Always use --repo spiriMirror/libuipc to reference the upstream repository (works with forks).

2. Verify the Working Branch

Follow the owner working agreements. Keep implementation commits on the current working branch; honor any different working branch explicitly selected by the owner.

3. Read Review Comments

gh pr view <PR_NUMBER> --comments --repo spiriMirror/libuipc

If the output is too long, store it in a temporary file for reference (output/ is gitignored):

mkdir -p output/.cursor
gh pr view <PR_NUMBER> --comments --repo spiriMirror/libuipc > output/.cursor/pr_comments.txt

Analyze all review comments and identify what needs to change.

Check the PR status, if there is a conflict, you need to resolve it first:

gh pr status --conflict-status --repo spiriMirror/libuipc

4. Plan & Implement Fixes

Analyze each review comment, then implement the focused fixes.

Build with the build command.

5. Test

Follow the same test procedure as fix-issue step 4:

  • Run relevant tests to verify the fix. See run-tests command.
  • Add new tests if the feedback requires new coverage.
  • Do NOT modify existing tests to make a fix pass.

6. Commit & Push

Use the commit command to format, commit, and push.

The PR will update automatically. Clean up any temporary files:

rm -rf output/.cursor

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