iterate-pr
Resolve PR Failures Until CI Passes
Pull request failures and scattered review feedback slow delivery. This skill investigates evidence, applies targeted fixes, and repeats checks until the branch is ready.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "iterate-pr" from https://skillstore.io/skills/davila7-iterate-pr.md and its manifest at https://skillstore.io/api/skills/davila7-iterate-pr/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "iterate-pr". Check the current pull request and report its status without changing files.
Expected outcome:
- Pull request 214 has two failed checks and one pending analysis check.
- Type checking fails in the billing module, while an integration test times out.
- No files were changed.
Using "iterate-pr". Investigate the failed checks and propose the smallest valid repair.
Expected outcome:
- The type error comes from an outdated return annotation in the billing adapter.
- The timeout is unrelated to this branch and has failed on the default branch.
- Recommended action: update one annotation, run the focused test, and request approval before committing.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown backticks and code fences. The shell substitution performs a fixed local branch lookup without an injection path. A medium-risk workflow issue remains because the skill stages all changes and pushes without explicit approval.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (29)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-iterate-pr/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-iterate-pr?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-iterate-pr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-iterate-pr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-iterate-pr.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). iterate-pr security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-iterate-pr/audits/9BibTeX citation
@techreport{davila7-davila7-iterate-pr-2026,
author = {davila7},
title = {iterate-pr security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-iterate-pr/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "iterate-pr security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/davila7-iterate-pr/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-iterate-pr:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
davila7-iterate-pr
2026-08-21
sickn33-iterate-pr
2026-08-21
getsentry-iterate-pr
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Repair a Failing Feature PR
Trace failed checks, fix the responsible code, and monitor the next CI run.
Process Review Feedback
Collect human and automated comments, validate each concern, and address only confirmed issues.
Prepare a Release Branch
Verify required checks, investigate remaining failures, and report blockers before release approval.
Try These Prompts
Check the current pull request. Report failing or pending CI checks and summarize unresolved review feedback. Do not change files.
Investigate failed CI logs for the current pull request. Explain each root cause, then propose the smallest targeted fixes before editing.
Address valid CI failures and review comments. Show planned files, make targeted changes, run relevant tests, then request approval before committing.
Iterate until required checks pass. Validate feedback, make minimal fixes, test, and pause before each commit or push. Stop after three repeated failures.
Best Practices
- Review failed logs and relevant source before modifying code.
- Inspect repository status and diffs before staging any file.
- Request explicit approval before each commit and remote push.
Avoid
- Do not infer a root cause from a check name alone.
- Do not stage unrelated changes with a broad repository command.
- Do not repeat the same failed repair more than three times.