Analyze repository diffs to identify defects, security risks, and structural problems.
npx skills add https://github.com/yanochka11/harness_bro --skill review-yanochka11
Please help me install this Agent Skill. Skill: review Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/curated/gstack/review Command: npx skills add https://github.com/yanochka11/harness_bro --skill review-yanochka11
This Skill helps engineers detect structural issues, security risks, and correctness problems in code changes before merging or landing a pull request.
Use the review skill to check my current diff for issues before I merge this pull request.
High-intent search queries and answers about installing and using this skill.
To analyze a git diff for security risks, use pre-landing code review to inspect changes against a base branch. This process identifies SQL safety issues, trust boundary problems, and side effects to ensure implementation safety before deployment.
Pre-landing code review is the process of evaluating code changes for defects and structural problems before merging. You need it when preparing a pull request to find actionable issues and apply fixes before reviewers or users encounter defects.
Check your current diff by applying specialized review checks across security, performance, API contracts, migrations, testing, and design. This validates implementation correctness and maintainability by inspecting the repository diff before deployment.
You can detect SQL safety and trust boundary problems by analyzing code changes before landing a pull request. The review process evaluates diffs against a base branch to identify these specific security risks and structural issues.
During pull request reviews, structural problems found include side effects, maintainability concerns, API contract violations, and design-related issues. The review evaluates changes across security, performance, migrations, and testing to validate implementation safety.
Yes, you need access to repository diffs and code analysis tools to perform a pre-landing code review. This access is required to validate implementation safety, maintainability, and correctness before deployment or merging.
luicabref97Reconcile FPF knowledge base with git diffs and update baseline.
Prathmesh2000Identify defects, security vulnerabilities, performance issues, and maintainability problems in code changes.
gkganesh12Audit source code against documentation and test suites for architectural drift.
thisisqubikaAnalyze code repositories for vulnerabilities using SAST and AI triage.
