Review open pull requests against project documentation and architectural requirements.
npx skills add https://github.com/erclx/aitk --skill claude-pr-review-erclx
Please help me install this Agent Skill. Skill: claude-pr-review Source: https://github.com/erclx/aitk/tree/main/claude/skills/claude-pr-review Command: npx skills add https://github.com/erclx/aitk --skill claude-pr-review-erclx
This skill solves the issue of isolated pull request reviews by providing an independent, cross-referenced analysis that considers project roadmaps, architecture, and downstream consumer impacts which a self-review often misses.
Ask the assistant to review the current pull request by providing the command to review the PR.
High-intent search queries and answers about installing and using this skill.
Automated pull request reviews fetch PR diffs and verify code changes against project-specific markdown documentation, architectural requirements, and roadmap context. This ensures integration and consumer-level compliance by posting structured findings directly to GitHub.
A multi-pass code review process performs an initial review followed by a close-out confirmation. This dual-pass approach ensures that findings from the first pass are addressed and verified before human approval of the pull request.
Yes, GitHub CLI integration is required. The automated code review operates by fetching PR diffs and posting structured findings to GitHub, which depends on the gh command-line tool and git to verify commit history.
Context-aware code review improves quality assurance by cross-referencing code changes with project roadmaps, architecture, and downstream consumer impacts. This provides high-signal feedback that isolated self-reviews often miss.
Yes, you can validate pull requests against established architectural standards. The review process integrates project-specific documentation and requirements to ensure code changes comply with the broader technical architecture.
Automated PR reviews require access to project-specific markdown documentation to validate changes. Without established documentation or roadmap context available, the review cannot provide high-signal architectural or consumer-level compliance feedback.
tonombConfigure issue trackers, triage labels, and documentation layouts across GitHub, GitLab, and local markdown.
yun520-1Analyze code commits and pull requests for bugs, vulnerabilities, and performance issues.
huidgeAnalyze git diffs to generate structured code-review feedback and inline comments.
jorgealvesAnalyze code diffs to identify bugs, style violations, and logic errors.
