Review diffs against coding standards and spec alignment in parallel.
npx skills add https://github.com/Flowm/dotfiles --skill code-review-flowm
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/code-review Command: npx skills add https://github.com/Flowm/dotfiles --skill code-review-flowm
This Skill solves the problem of incomplete code reviews that only check either code style or spec compliance, missing critical issues that fall through the gaps of single-axis review processes.
Use the code-review skill to review all changes between your current feature branch and the main branch for both standard compliance and spec alignment.
High-intent search queries and answers about installing and using this skill.
You can review a feature branch for coding standards and spec compliance by running a parallel two-axis diff review against HEAD. This isolates standards and spec checks in separate sub-agents to prevent context pollution, then aggregates findings side-by-side for clear reporting.
Checking a git diff for code smells and missing PRD requirements is best done via dual-axis review. It simultaneously evaluates repository coding standards and spec alignment in isolated sub-agents, catching both style violations and missing requirements in a single pass.
Yes, you can review a specific commit range for spec alignment by defining the fixed point and HEAD using SHAs, tags, branches, or merge bases. The skill processes the diff between these points to identify any spec compliance gaps.
Parallel code review prevents context overlap by running style and spec checks in isolated sub-agents. This separation ensures that coding standards evaluation does not pollute the spec compliance analysis, yielding unambiguous side-by-side findings.
You need to isolate coding standards checks from spec compliance checks when single-axis review processes miss critical issues. Isolating these checks into separate sub-agents prevents context overlap and ensures both style violations and spec gaps are caught clearly.
Yes, you can use this branch review approach for work-in-progress changes before a pull request. It evaluates diffs between your current state and a fixed point, catching early style violations and missing spec requirements prior to PR submission.
JetaofgakDispatch a code-review subagent to assess changes between git SHAs.
willdadyCompare git diffs against coding standards and project specifications.
gotalabTransforms Notion spec documents into actionable implementation plans and tasks with progress tracking.
metabaseReview Clojure and ClojureScript diffs for Metabase coding standard violations.
