Aha! *_/
npx skills add https://github.com/BasharAmso/Bashi --skill code-review-basharamso
Please help me install this Agent Skill. Skill: Code Review Source: https://github.com/BasharAmso/Bashi/tree/main/create-bashi-app/template/.claude/skills/code-review Command: npx skills add https://github.com/BasharAmso/Bashi --skill code-review-basharamso
Code reviews are often inconsistent, time-consuming, and miss critical issues. This skill provides a structured two-pass review (CRITICAL first, then INFORMATIONAL) with interactive issue resolution to improve code quality, security, and maintainability, while referencing scope challenges, failure modes, and TODOS for traceability.
Trigger a CODE_REVIEW_REQUESTED for changed files and accept the generated findings to update the project state.
High-intent search queries and answers about installing and using this skill.
Conduct a structured code review by analyzing file diffs using a two-pass approach to surface critical correctness issues first, followed by informational best practices. This process checks maintainability against project decisions and generates a traceable verdict.
A two-pass code review process isolates critical findings before evaluating informational improvements. You need this process to ensure severe correctness and security issues are addressed first, preventing high-severity problems from being buried in routine diff analysis.
Trace code review findings by consulting DECISIONS.md and TODOS.md during diff analysis. This ensures the code aligns with architectural goals, and the generated review summary updates STATE.md to maintain traceable outcomes across the software engineering lifecycle.
Yes, you can use this skill for large-scale software engineering projects because it enforces a structured two-pass review at scale. It consults existing project sources and state files to maintain alignment with architecture and goals across extensive codebases.
The best way to find high-severity issues in a diff is applying a structured two-pass review that consults a code-review checklist. This surfaces CRITICAL findings first, ensuring severe correctness and maintainability problems are resolved before informational ones.
Yes, you need a checklist.md file to review code for best practices. The skill consults this checklist alongside DECISIONS.md and TODOS.md to evaluate correctness and maintainability, producing actionable findings and a final project state update.
KuassGenerate project.md, roadmap.md, and state.md from templates with user input.
Khang5687Monitor ClawSweeper workflow status via GitHub API events.
CyapstayeEnforce the Red-Green-Refactor cycle with failing tests before implementation.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
