itx-review-pr
Skill67 starsChanged 2 months agoApache-2.0View on GitHub
Request code review for a pull request
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clawctl-lmworkSkill
- clawctlSkill
- clawctl-uatSkill
- create-playwrightSkill
- create-vhsSkill
- itx-bug-newSkill
- itx-bug-updateSkill
- itx-executeSkill
- itx-issue-newSkill
- itx-issue-updateSkill
- itx-noteSkill
- itx-plan-createSkill
- itx-plan-scaffoldSkill
- itx-pr-statusSkill
- itx-releaseSkill
- itx-triageSkill
- itx-verifySkill
- sync-upstreamSkill
- tddSkill
- blog-authorSkill
- daily-digestSkill
- docs-syncSkill
- issue-triageSkill
- release-watcherSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If PR number provided, use it
- Distinctive: line 15
If not, find PR for current branch:
- Very specific: line 48
ATX via CLI: Check command -v atx and require atx server status to report Running: true.
- Distinctive: line 56
If the CLI is unavailable, stopped, fails, or times out, continue to manual review.
- Distinctive: line 58
Manual review: After both automated transports are exhausted, use the manual checklist below and state clearly which attempts were …
- Distinctive: line 63
If rating <= 3/5 or blocking issues exist:
- Distinctive: line 66
If rating > 3/5 and no blockers:
- Distinctive: line 91
Use this checklist when automated review is disabled or no ATX transport is available:
- Distinctive: line 251
Use suggestions to improve code quality
- Distinctive: line 252
Update PR description with review findings
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PR Review
Request a code review for a pull request.
Instructions
- Identify PR:
- If PR number provided, use it
- If not, find PR for current branch:
gh pr view --json number,title,url
- Get PR Details:
gh pr view <number> --json number,title,body,files,additions,deletions gh pr diff <number> - Check Review Configuration:
ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json" if [ -f "$ITX_CONFIG" ]; then REVIEW_ENABLED=$(jq -r '.mcp.review_enabled // false' "$ITX_CONFIG") else REVIEW_ENABLED="false" fi - Execute Review:
If Automated Review Enabled
Attempt each transport in order. Tool identifiers differ by harness, so do not invoke a configured or example name unless it is available in the current harness. An unavailable, failed, or timed-out attempt falls through to the next step.
- ATX via MCP: Inspect the current tool list for an ATX request-review
tool. If one is available, invoke it with
Review PR #<number>. If MCP is unavailable, fails, or times out, continue to the CLI step. - ATX via CLI: Check
command -v atxand requireatx server statusto reportRunning: true. If both checks pass, run the stateless review command so the result does not depend on harness-specific hooks:
If the CLI is unavailable, stopped, fails, or times out, continue to manual review.atx review request \ --prompt "Review PR #<number>, including its full diff and tests." \ --format json --timeout 15m - Manual review: After both automated transports are exhausted, use the manual checklist below and state clearly which attempts were unavailable or failed.
Process Automated Review Results:
- If rating <= 3/5 or blocking issues exist:
- List issues to fix
- Recommend specific changes
- If rating > 3/5 and no blockers:
- PR is ready for merge
Report:
## Automated Review Summary
**PR**: #<number> - <title>
**Rating**: <X>/5
### Blocking Issues
<table or "None">
### Warnings
<list or "None">
### Suggestions
<list or "None">
### Verdict
<READY FOR MERGE / NEEDS CHANGES>Manual Review
Use this checklist when automated review is disabled or no ATX transport is available:
Review Checklist:
- Code Quality:
- Code follows project conventions and style
- No obvious bugs or logic errors
- Error handling is appropriate
- No security vulnerabilities (injection, XSS, etc.)
- No hardcoded credentials or secrets
- Testing:
- Tests added for new functionality
- Existing tests still pass
- Edge cases are covered
- Test coverage is adequate
- Documentation:
- Code is self-documenting or has comments where needed
- Public APIs are documented
- README updated if needed
- Architecture:
- Changes align with existing patterns
- No unnecessary complexity
- Dependencies are justified
- Performance considerations addressed
- PR Hygiene:
- PR title and description are clear
- Commits are logical and well-named
- No unrelated changes included
- Links to related issues
Report:
## Manual Review Summary
**PR**: #<number> - <title>
### Review Checklist Results
#### Code Quality: /
<findings>
#### Testing: /
<findings>
#### Documentation: /
<findings>
#### Architecture: /
<findings>
#### PR Hygiene: /
<findings>
### Issues to Address
<list blocking issues or "None">
### Suggestions
<list improvements or "None">
### Verdict
<READY FOR MERGE / NEEDS CHANGES>- Add Review Comment (for both modes):
Post review summary as PR comment:
gh pr comment <number> --body "<review summary from above>" - Update Issue Status (if configured):
# Check if project board is enabled ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json" if [ -f "$ITX_CONFIG" ]; then PROJECT_ENABLED=$(jq -r '.github.project_board.enabled // false' "$ITX_CONFIG") if [ "$PROJECT_ENABLED" = "true" ]; then # Extract repo info REMOTE_URL=$(git config --get remote.origin.url) OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's/.*[:/]([^/]+\/[^/]+)(\.git)?$/\1/') OWNER=$(echo "$OWNER_REPO" | cut -d'/' -f1) REPO=$(echo "$OWNER_REPO" | cut -d'/' -f2) # Load project config PROJECT_ID=$(jq -r '.github.project_board.project_id' "$ITX_CONFIG") STATUS_FIELD_ID=$(jq -r '.github.project_board.status_field_id' "$ITX_CONFIG") IN_REVIEW_ID=$(jq -r '.github.project_board.status_options.in_review' "$ITX_CONFIG") # Get issue number from PR ISSUE_NUM=$(gh pr view <number> --json number --jq '.number') NODE_ID=$(gh api repos/$OWNER/$REPO/issues/$ISSUE_NUM --jq '.node_id') # Get project item ID ITEM_ID=$(gh api graphql -f query=' query($projectId: ID!, $contentId: ID!) { node(id: $projectId) { ... on ProjectV2 { items(first: 100) { nodes { id content { ... on Issue { id } } } } } } } ' -f projectId="$PROJECT_ID" -f contentId="$NODE_ID" | \ jq -r ".data.node.items.nodes[] | select(.content.id == \"$NODE_ID\") | .id") # Update status to In Review gh project item-edit --project-id "$PROJECT_ID" --id "$ITEM_ID" \ --field-id "$STATUS_FIELD_ID" --single-select-option-id "$IN_REVIEW_ID" fi fi
Configuration
Enable automated review in .claude/itx-config.json:
{
"mcp": {
"review_enabled": true
}
}The mcp key is retained for configuration compatibility. The workflow
detects an ATX MCP tool exposed by the active harness, then falls back to the
atx CLI and finally to manual review; it does not pin a harness-specific tool
identifier in shared configuration.
Default (no config): Manual review mode with checklist
See CONFIG.md for full configuration options.
Notes
Automated Review Mode:
- Automated specialist reviews
- Faster turnaround
- Uses an available ATX MCP tool or the
atxCLI - Rating-based approval (> 3/5)
Manual Review Mode:
- Comprehensive checklist-based review
- No external dependencies
- Requires human reviewer
- Detailed findings documentation
Best Practices:
- Review promptly after PR creation
- Address all blocking issues before merge
- Use suggestions to improve code quality
- Update PR description with review findings
Prompt Logging
REQUIRED: Append prompt log to .itx/<N>/02_VERIFY.md.
See AGENTS.md for format specification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

