Review pull request diffs for correctness, safety, and boundary issues.
npx skills add https://github.com/codetail-ai/skillwright --skill review-codetail-ai
Please help me install this Agent Skill. Skill: review Source: https://github.com/codetail-ai/skillwright/tree/main/registry/skills/review Command: npx skills add https://github.com/codetail-ai/skillwright --skill review-codetail-ai
This Skill helps you review code changes before they land, so you catch correctness bugs, safety issues, and boundary mistakes before they reach users.
Use the review skill to inspect the current pull request diff and flag any real bugs, safety risks, or missing cases before merging.
High-intent search queries and answers about installing and using this skill.
To review a pull request diff for SQL safety and race conditions, analyze the changed files against the base branch to flag correctness bugs, boundary issues, and safety risks before the code lands.
An LLM trust boundary check during code review verifies whether untrusted inputs cross security limits unexpectedly. Inspect the pull request diff to find boundary mistakes and safety issues before the code reaches users.
Yes, you can use an automated pre-merge check to catch shell injection vulnerabilities by reading the changed files and surrounding project context to verify whether each security issue is real and actionable before shipping.
The best way to find enum completeness gaps in a pre-landing code review is to apply structural checks against the pull request diff, verifying that all cases are covered and flagging missing entries before the code lands.
Pre-merge diff analysis requires reading the changed files and the surrounding project context to verify whether each issue is real and actionable, ensuring correctness and safety checks are accurate before landing code.
rioX432Review branch changes against the base branch for bugs, security, architecture, and quality issues.
a29paulDetects SQL injection, LLM trust boundary violations, race conditions, and enum gaps in pull request diffs.
fghaffarAnalyze git diffs for SQL safety, race conditions, and LLM trust boundaries.
diiviikk5Analyze PR diffs for SQL safety, LLM trust boundaries, and structural issues.
