Evaluate change proposals against work unit contracts and evidence requirements.
npx skills add https://github.com/tesserine/groundwork --skill code-review-tesserine
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/tesserine/groundwork/tree/main/skills/code-review Command: npx skills add https://github.com/tesserine/groundwork --skill code-review-tesserine
Review governance ensures proposed changes are safe to advance, not a formal style pass or forge operation, evaluating against work units, behavior contracts, implementation plans, and verification evidence to classify findings as blocking or non-blocking.
Review a pending change proposal and determine blocking or non-blocking findings using the focus areas, then document your verdict.
High-intent search queries and answers about installing and using this skill.
Rigorous code review evaluates proposed changes against work unit contracts and evidence requirements to classify findings as blocking or non-blocking. It checks scope honesty, correctness, semantic-shift detection, and documentation impact to ensure changes are safe to advance.
Scope honesty in code review verifies that a proposed implementation stays strictly within the boundaries of its claimed work unit. You need to check it whenever reviewing change proposals to prevent unauthorized modifications from advancing undetected.
Detect semantic shifts during code verification by applying correctness checks across interfaces, schemas, and tests. This process identifies breaking changes in behavior contracts and classifies them as blocking findings based on evidence quality.
Evidence-driven code review requires explicit verification artifacts and implementation plans to assess documentation impact and fix-or-file discipline. These inputs provide the necessary context to evaluate whether a change proposal meets safety standards.
Classify blocking versus non-blocking findings by evaluating scope honesty, correctness, evidence quality, and documentation impact against the work unit contract. This review governance approach ensures only safe, verified changes advance to the next stage.
Code review governance limitations include its focus on review safety rather than formal style passes or forge operations. It evaluates correctness and evidence quality but does not execute or compile the proposed implementation artifacts directly.
adacosdevExecute verification workflows to generate compliance reports against specs and designs.
daddiaEvaluate solution.md against architecture quality gates and amend findings.
antigravityos187-sketchDetect circular dependencies, coupling issues, and layer violations with jCodemunch.
alangebRun pyscan, pyanalyze, ruff, and black to generate a unified markdown report.
