Analyze diffs against the base branch and auto-fix mechanical issues during PR reviews.
npx skills add https://github.com/g4rcez/dotfiles --skill review-g4rcez
Please help me install this Agent Skill. Skill: review Source: https://github.com/g4rcez/dotfiles/tree/main/.ai/skills/review Command: npx skills add https://github.com/g4rcez/dotfiles --skill review-g4rcez
Pre-landing PR reviews often miss subtle SQL safety, data trust boundaries, and consistency checks that can introduce defects into production. This Skill provides structured guidance and automation to surface these issues before merging.
Run the review workflow against the current branch to surface PR diff findings and recommendations.
High-intent search queries and answers about installing and using this skill.
Pre-landing PR review automation analyzes branch diffs against the base branch to surface SQL safety, LLM trust boundaries, and data consistency issues. It applies a two-pass CRITICAL and INFORMATIONAL checklist to prioritize fixes before merging.
The best way to auto-fix mechanical issues in a pull request diff is using a fix-first workflow that applies automated corrections while prompting for human input on ambiguous items. This ensures mechanical defects are resolved without overlooking complex review concerns.
A two-pass checklist workflow executes a CRITICAL pass first to identify high-risk defects like SQL safety issues, followed by an INFORMATIONAL pass for less urgent concerns. This structured approach reduces risk by prioritizing fixes before delivering actionable findings.
Yes, you can integrate Greptile with pre-landing PR review automation to surface external review comments and triage discussions. This integration enriches the diff analysis by pulling in contextual feedback from external sources during the review workflow.
Automated diff analysis detects enum completeness and consistency issues by evaluating code changes against a structured review checklist. It surfaces these concerns alongside SQL safety and trust boundary checks to prevent defects from reaching production.
You should prompt for human input during automated PR review when the diff analysis encounters ambiguous items that cannot be auto-fixed mechanically. The fix-first approach handles clear defects autonomously while escalating uncertain findings for manual decision-making.
AkbarDevopIdentify production-risk findings in a code diff before merging.
dogearedAutomate the release workflow from PR merge to production deployment with health checks.
maruinaEvaluate GitHub PR review comments against current repository state.
vertivolatamRun static analysis across multiple programming languages with linters and security scanners.
