Review code changes for correctness, security, style, architecture, and testing issues.
npx skills add https://github.com/supertyrelle/pelley --skill review-supertyrelle
Please help me install this Agent Skill. Skill: review Source: https://github.com/supertyrelle/pelley/tree/main/skills/review Command: npx skills add https://github.com/supertyrelle/pelley --skill review-supertyrelle
This Skill helps you perform a disciplined code review so you can catch bugs, security risks, design drift, and missing tests before changes are merged.
Review the staged changes in this repository and return prioritized findings with evidence, severity, and a clear merge verdict.
High-intent search queries and answers about installing and using this skill.
To check staged git diffs, the review process evaluates code changes across correctness, security, style, architecture, and testing dimensions. It analyzes full file context and traces code paths to produce severity-ranked findings with actionable merge guidance.
The best way to perform an automated code review on a pull request is using scope-aware diff analysis. This evaluates staged changes or commit ranges, classifies findings by severity with concrete evidence, and returns a clear merge verdict.
Yes, you can review file-specific git changes. The analysis applies to individual file modifications, reading the full file context to identify design drift, architecture issues, and missing tests before producing a final merge verdict.
Code review analysis works with both staged changes and commit ranges. It evaluates the full scope of provided changes, traces code paths to classify severity, and generates actionable evidence for pre-merge quality checks.
Automated pre-merge quality checks identify missing tests by reading full file context and tracing code paths within the diff. The review classifies these testing gaps by severity and provides actionable evidence in the final merge verdict.
When reviewing code changes, limitations depend on providing full file context. The analysis requires reading complete files to trace code paths and classify security or style findings accurately; incomplete context may reduce the accuracy of the merge verdict.
nilleReview code diffs for correctness, security, and conventions.
tyevansAnalyze staged changes, commits, or pull requests for code issues.
HerbertJulioReview changed files for architecture, types, security, and test coverage.
az9713Run a seven-dimension pre-merge review and generate a COMPREHENSION_ARTIFACT.md verdict.
