MichaelVessia/fix-pr
modules/programs/agents/shared/skills/fix-pr/SKILL.md
Autonomously fix a pull request by resolving relevant failing PR checks, then addressing PR comments and posting replies. Use when user says "fix pr", "prfix", "fix PR checks", "address PR feedback", or asks to clean up a PR end to end.
$ install --global
skillsauthnpx skillsauth add MichaelVessia/nixos-config fix-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 12:33 PM10.4s1 file scanned
SKILL.md
- name:
- fix-pr
- description:
- |
- allowed-tools:
- Bash(gh *), Bash(git *), Bash(npm test*), Bash(bun test*), Bash(pnpm test*), Bash(yarn test*), Read, Edit, Write, Glob, Grep, TodoWrite, Skill
fix-pr
Arguments: $ARGUMENTS (optional PR number or URL).
Execute this flow fully, stop only if blocked.
1) Resolve target PR
- Determine PR target:
- If
$ARGUMENTShas PR URL/number, use it. - Else use current branch PR:
gh pr view.
- If
- Load PR context:
- Number, URL, title, body, head ref, head SHA.
- Changed files list from
gh pr diff --name-only.
2) Resolve merge conflicts
- Check if the PR has merge conflicts:
- Use
gh pr view <PR> --json mergeable,mergeStateStatus.
- Use
- If conflicts exist, invoke
resolve-merge-conflictswith the PR number. - After resolution, push and confirm the PR is conflict-free before proceeding.
3) Fix relevant failing checks
- Inspect checks for this PR:
- Use
gh pr view <PR> --json statusCheckRollup. - Also inspect recent workflow runs for PR head SHA with
gh run listand details viagh run view --log-failed.
- Use
- Build todo list of failing checks.
- For each failing check:
- Decide relevance to PR changes.
- Relevant when failure points to touched files, tests, lint, typecheck, build, or logic connected to changed code.
- Ignore clearly unrelated infra flakes (document why).
- For each relevant failure:
- Reproduce locally when possible.
- Implement fix from first principles.
- Run targeted tests/checks for changed area.
- Commit and push immediately after passing checks.
- Use clear commit message, no AI attribution text.
- Re-query PR checks. Continue until no relevant failures remain.
4) Address PR comments
Invoke address-pr-feedback to review and address all open PR comments. The
skill handles gathering comments, creating a todo list, implementing fixes,
running tests, and committing changes.
5) Reply on PR via gh-comment
After address-pr-feedback completes, invoke gh-comment to post replies for
each processed comment. Include:
- Comment reference (author + file:line when present)
- Decision (
addressedornot addressed) - What changed (commit SHA summary) or why skipped
Keep replies factual and brief.
6) Done criteria
Complete only when all are true:
- PR has no merge conflicts.
- No relevant failing PR checks remain.
- Every gathered PR comment has been evaluated.
- Accepted comments have fixes committed and pushed.
- PR replies were posted through
gh-comment.
If blocked (missing permissions, failing external service, ambiguous feedback), stop and report exact blocker plus next required user action.
Related Skills
MichaelVessia/bro
development
VerifiedTrustedCommunity
Restate the last message in plain human language, with no jargon.
2SKILL.mdUpdated Jul 23, 2026
MichaelVessia/fanout-prs
testing
VerifiedTrustedCommunity
Fan out a batch of work items into one PR each via isolated worktree agents, review every PR before it opens, then babysit all PRs through green CI and review feedback. Use when the user wants to fan out PRs, dispatch parallel PR agents over a list of items, or run a batch of independent changes as separate PRs.
2SKILL.mdUpdated Jul 10, 2026
MichaelVessia/herdr-dispatch
development
VerifiedTrustedCommunity
Dispatch user-visible coding or research agents through Herdr with Codex-Desktop-like thread ergonomics. Use when the user asks to use Herdr to spawn, dispatch, fan out, inspect, follow up with, or monitor agent workspaces/threads.
2SKILL.mdUpdated Jun 30, 2026
MichaelVessia/plannotator-visual-explainer
development
VerifiedTrustedCommunity
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
2SKILL.mdUpdated Jun 12, 2026