Iterate Pr

What it does

The source uses separate helpers for checks, feedback, monitoring and replies. It distinguishes pending automated work from human review gates and draft readiness, so passing tests does not automatically become permission to merge. Its loop emphasizes diagnosing a failure before changing code.

Best for

Maintaining an existing pull request whose CI or concrete reviewer findings require focused follow-up work.

Tradeoffs and requirements

The bundled helpers require inspection, authenticated GitHub access and their declared tooling. Posting replies or changing PR state is a separate external action. Bot-priority rules and feedback buckets reflect the publisher’s process and may not suit another repository.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/getsentry/skills/tree/d12f250460ffd961f549dbebf7eeb0cf4afd4c2e/skills/iterate-pr --skill iterate-pr

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

55/100

55

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Resolve the target PR, collect its current checks and substantive feedback, then fix a confirmed cause in a small change. Re-run the relevant checks before considering another iteration.

How to judge the result

Read back the latest checks and unresolved findings after pushing. Report human approval and merge gates explicitly, preserve draft status unless authorized, and distinguish a completed technical fix from a decision that still belongs to the owner.