com um clique
nitpick-nuker
Autonomous PR comment triage - fixes review feedback until CI passes
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Autonomous PR comment triage - fixes review feedback until CI passes
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Generate professional documentation for IntexuraOS services (apps, workers, packages). Produces 5 doc files per service, 3 per package, plus aggregated site content and cross-validation reports. Supports interactive, autonomous, and team-of-agents modes. Use when documenting services, generating docs, updating documentation, or validating doc consistency.
Orchestrate a 6-phase release workflow with automated service documentation, high-level docs updates, README "What's New" section, website improvements, and semantic versioning. Use when preparing a new release.
Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry.
Prepare an IntexuraOS release by collecting release data, triaging changes, updating docs, versions, changelog, website release highlights, and GitHub release notes.
Use when the user says "commit push", "commit and push", "push a PR", or asks Codex to finalize IntexuraOS changes by committing, pushing, and opening a pull request against development.
Use when user pastes a dev.intexuraos.cloud or intexuraos.cloud code-task URL and asks to debug, investigate, or understand what went wrong. Also use when user mentions a code task ID (task_*) with investigation intent.
| name | nitpick-nuker |
| description | Autonomous PR comment triage - fixes review feedback until CI passes |
| argument-hint | [PR_NUMBER] or run on current branch PR |
| user-invocable | true |
Autonomous PR comment triage that processes GitHub review comments, fixes actionable feedback, and loops until CI passes.
| Input | Action |
|---|---|
/nitpick-nuker | Triage PR for current branch |
/nitpick-nuker 616 | Triage PR #616 |
Execute the workflow at: .claude/skills/nitpick-nuker/workflows/triage-pr-comments.md
All scripts are in .claude/skills/nitpick-nuker/scripts/:
| Script | Purpose |
|---|---|
fetch-unprocessed-comments.sh | Fetch comments without 😄 from bot |
add-reaction.sh | Add 😄 reaction to processed comment |
reply-to-comment.sh | Post per-comment reply with reasoning |
post-summary.sh | Post summary comment to PR |
watch-ci.sh | Watch CI with workflow filtering |
The skill processes three types of comments:
issue_comment — General PR conversation commentsreview_body — The overall review summary textreview_comment — Inline code comments within a reviewBot comments (e.g. "Claude finished task", "Codex Review") are the PRIMARY source of review feedback. Bots post their full code reviews as issue_comment or review_body — these are NOT noise to skip. Always read the full body of bot comments; they typically contain detailed review findings, suggestions, and inline code feedback.
Every issue_comment must be read and verified. General comments may contain:
Never auto-skip an issue_comment based on author alone. Read the body first.
For each comment, decide:
| Criteria | Action |
|---|---|
| Clear actionable fix (typo, style, naming) | FIX |
| Code change with clear intent | FIX |
| Bot review with actionable findings in body | FIX (extract and address each) |
| User instruction (skip X, focus on Y) | FOLLOW — adjust processing scope |
| Question or discussion | SKIP - "Discussion/question" |
| Disagree with suggestion | SKIP - "Intentional design" |
| Already addressed elsewhere | SKIP - "Addressed in other fix" |
| Outside PR scope | SKIP - "Out of scope" |
| Pure status/coverage report with no suggestions | SKIP - "Automated report" |
After applying fixes:
1. Commit with message listing addressed comments
2. Push
3. Run watch-ci.sh (ignores zai-claude-code-review.yml)
4. If CI fails:
a. Analyze failure
b. Fix the issue
c. Goto step 1
5. Continue until CI green
Posted at end of PR after each run. Template at: .claude/skills/nitpick-nuker/templates/summary-comment.md