code-review
79Review Code with Sentry Practices
Pull request reviews often miss risks across correctness, security, performance, and testing. This skill gives Claude, Codex, and Claude Code a structured Sentry review checklist.
Iterate Pull Requests Until CI Passes
Pull request fixes often require repeated CI checks, review updates, and careful commits. This skill guides Claude, Codex, or Claude Code through a controlled feedback, fix, push, and wait cycle.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
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/getsentry-iterate-pr.md and its manifest at https://skillstore.io/api/skills/getsentry-iterate-pr/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "iterate-pr". Run the skill on my current branch and stop after diagnosing the first failure.
Expected outcome:
Using "iterate-pr". Address valid review feedback and prepare a follow-up commit for review.
Expected outcome:
Using "iterate-pr". Continue the pull request iteration until CI is green, but stop after repeated failures.
Expected outcome:
The main confirmed risks are authenticated external commands that read GitHub data and mutate the repository. The highest-impact behavior is the commit and push loop, which can publish local changes if used without review. Several static detections were false positives caused by Markdown backticks around labels, service names, and headings.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/getsentry-iterate-pr/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/getsentry-iterate-pr?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/getsentry-iterate-pr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/getsentry-iterate-pr/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/getsentry-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>getsentry. (2026). iterate-pr security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/getsentry-iterate-pr/audits/7@techreport{getsentry-getsentry-iterate-pr-2026,
author = {getsentry},
title = {iterate-pr security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/getsentry-iterate-pr/audits/7},
note = {Author version unspecified}
}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 7)"
version: "unspecified"
type: report
authors:
- name: "getsentry"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/getsentry-iterate-pr/audits/7"
identifiers:
- type: other
value: "skillstore:getsentry-iterate-pr:audit:7"
description: "Skillstore immutable audit report identifier"
Each 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
A developer can diagnose failing checks, address valid review comments, and prepare a focused follow-up commit.
A maintainer can inspect check status and failed logs before deciding which failures need code changes.
A team member can gather human and bot feedback, verify it, and organize the next PR update.
Use iterate-pr on the current branch. Identify the pull request, check CI, and report the first actionable failure before editing.
Use iterate-pr to gather review comments and bot comments. Verify each item, then fix only valid feedback.
Use iterate-pr to inspect failed CI logs. Make minimal fixes and ask before committing or pushing changes.
Use iterate-pr with a maximum of two fix attempts. Confirm before every commit or push, and summarize CI and review evidence.
Author
getsentryLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
30c73eac2afe762f6aa9c4553158769369d47351
Maintenance freshness
7/18/2026
Usage
5 downloads ยท 299 views
File structure
๐ SKILL.md
Review Code with Sentry Practices
Pull request reviews often miss risks across correctness, security, performance, and testing. This skill gives Claude, Codex, and Claude Code a structured Sentry review checklist.
Clean Up AI-Generated Code Changes
AI-assisted branches often include extra comments, unnecessary defensive code, and weak type workarounds. This skill reviews the branch diff and removes changes that do not match the surrounding code style.
Create Sentry-Style Pull Requests
Writing clear pull requests takes context and review discipline. This skill guides Claude, Codex, and Claude Code through Sentry-style PR preparation.
Review Branch Changes for Bugs
Branch reviews often miss security defects, regressions, and untested edge cases. This skill guides Claude, Codex, and Claude Code through a structured audit.
Write Sentry Commit Messages
Teams lose time fixing vague or inconsistent commit history. This skill helps Claude, Codex, and Claude Code draft Sentry-style conventional commits with clear issue references.
Audit Claude Code Permissions
Unsafe or missing Claude Code permissions can slow repository setup and create avoidable risk. This skill inspects project tooling and proposes settings that match detected files and services.
Create Consistent GitHub Issues
by C0ntr0lledCha0s
Poorly structured issues create ambiguity and require manual cleanup. This skill drafts and validates titles, bodies, labels, milestones, projects, and relationships.
Review Code with Structured Quality Checks
by alirezarezvani
Code reviews can miss quality, security, and maintainability issues. This skill guides structured reviews with scripts, checklists, and report generation.
Build Claude Code Agents
by C0ntr0lledCha0s
Creating reliable AI agents requires clear schemas, safe tools, and repeatable review steps. This skill guides agent design, validation, migration, and maintenance for Claude Code workflows.
Build Claude Code Slash Commands
by C0ntr0lledCha0s
Teams need repeatable AI workflows that are easy to invoke and review. This skill helps create, update, validate, and document Claude Code slash commands.
Build Reliable PowerShell Tools
by hmohamed01
PowerShell projects need consistent structure, safe parameters, and current module guidance. This skill helps create scripts, modules, and GUIs using practical PowerShell references.
Manage Coding Agent Workflows
by kiwi-phantomworks
Coding-agent projects can drift when tasks, scope, and checks are vague. This skill gives PM templates and review rules that keep Claude, Codex, and Claude Code work bounded and verifiable.