Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jerseycheese/agent-skills --skill pr-review-fix-pipelinegit clone --depth 1 https://github.com/jerseycheese/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jerseycheese/agent-skills/pr-review-fix-pipeline)<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/pr-review-fix-pipeline"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/pr-review-fix-pipeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/pr-review-fix-pipeline"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/pr-review-fix-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.01533 |
| Opus 5.5 | $0.00032 | $0.00613 |
| Sonnet 5.5 | $0.00016 | $0.00307 |
| Haiku 4.5 | $0.00008 | $0.00153 |
Grade A, and why
pr-review-fix-pipeline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous PR Review & Fix Pipeline
When to Use This Skill
Use this skill when:
- You want both review AND automatic fixes in one workflow
- PR has blocking issues that need immediate resolution
- You trust Claude to apply non-controversial fixes (typos, lint errors, obvious bugs)
- You want to minimize back-and-forth between review and implementation
⚠️ Important Notes
This is an autonomous workflow that will:
- Review the PR
- Apply fixes for blocking issues
- Run tests and lint
- Commit changes
- Push to the PR branch
Only use this when:
- You're comfortable with Claude modifying code without asking
- The PR is on a feature branch (not main/develop)
- You can review the resulting diff before merging
Pipeline Steps
Step 1: Fetch and Analyze
-
Get PR information
gh pr view [NUMBER] --json headRefName,baseRefName,title,body -
Fetch the diff (never cached)
gh pr diff [NUMBER] -
Checkout the PR branch
git fetch origin [HEAD_REF] git checkout [HEAD_REF]
Step 2: Categorize Issues
Analyze every file change and categorize issues:
-
[BLOCKING]: Must be fixed before merge
- Bugs and logic errors
- TypeScript errors
- Breaking changes
- Security issues
- Missing error handling
-
[RECOMMENDATION]: Should be fixed but not critical
- Performance improvements
- Better patterns available
- Code style issues
-
[NIT]: Nice-to-have improvements
- Whitespace, formatting
- Comment improvements
- Variable naming
Step 3: Auto-Fix Blocking Issues
For each [BLOCKING] issue:
-
Create a Task sub-agent to implement the fix
Task: Fix [specific issue] Context: [issue description and location] Constraint: Only fix this specific issue, don't refactor -
Wait for sub-agent completion before proceeding to next issue
-
Track fixes with TodoWrite for visibility
Step 4: Run Validation (with Dev Server Protection)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago Changed · -1 lines · -25 tokens per session d743a345a436
- 1mo ago First seen · 253 lines · 106 tokens per session scan A 97aad2a3f83d
pr-review-fix-pipeline is a skill published in the GitHub repository jerseycheese/agent-skills (3 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 1,533 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
shipit
Turn finished work into a clean commit and pull request. Always asks first whether the commit and PR should carry AI/bot authorship attribution or stay fully human-authored, then matches the repository's existing commit conventions, splits work into logical commits, and writes a PR body with context, risk, and…
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
eg-precommit-review
Run a Codex-native pre-commit independent-review loop on pending changes.
everything-claude-code-conventions
Core repository standards for naming, structure, commits, and workflows.
ship
Review changed files with your project's review skill, fix findings, and commit; deploy with --deploy.