Reviews pending change sets with a lens panel and risk-gated automated fixes.
npx skills add https://github.com/matthewalton/speccle --skill review-matthewalton
Please help me install this Agent Skill. Skill: review Source: https://github.com/matthewalton/speccle/tree/main/packages/plugin/skills/review Command: npx skills add https://github.com/matthewalton/speccle --skill review-matthewalton
.speccle/lenses/*.md, each returning findings anchored to changed lines with severity, cause, and a proposed fix. - Risk-gated fixing: Runs speccle risk before the panel; below the threshold it fixes findings and re-runs the checks-gate after each fix, reverting any fix that goes red, while at or above the threshold it reports findings and stops for a human. - Remedy routing and calibration: Routes every finding to a durable prevention artefact (check, criterion, or lens), recalls prior remedies from the remedy record, and records the change against the calibration record before committing. - Use Case: Before opening a pull request on a feature branch, ask for a review of the pending change; the Skill scores the risk, runs the lens panel, fixes low-risk findings with the checks-gate guarding each one, commits the survivors, and closes with an overruleable summary. ## Quick Start Ask the assistant to review my pending changes and fix whatever the risk gate allows before I open a pull request.High-intent search queries and answers about installing and using this skill.
Ask to review the pending change or run the lenses. The Skill reads the working diff with git status and git diff HEAD, scores its risk, fans out the lens panel, fixes findings below the threshold, and lands verified fixes in one commit.
The speccle risk command computes a deterministic score and threshold from the change set, and a risk lens may escalate but never lower that floor. Below the threshold fixes are applied unasked; at or above it, findings are reported and a human is required.
A fix that turns the checks-gate red is reverted to its pre-fix state rather than patched around, and the finding is carried forward as unfixed. Only reds caused by the fix itself trigger a revert; pre-existing reds are reported in the summary.
No, findings CI has already posted on a pull request are handled by the separate address skill. This Skill derives findings locally from the pending change and never pushes or takes a pull request.
The repo must contain a .speccle/lenses/ directory with lens files, and the speccle CLI must resolve from the repo's node_modules, a global install, or a source clone. If lenses are missing, the Skill suggests running speccle init and stops.
open-octoConvert technical designs into tested code via dependency-ordered vertical slices.
questdbPosts an existing code review as an approving GitHub PR review and adds a merge-queue label.
citypaulInject mutations into production code and report killed, survived, and no-coverage mutants.
daodaoeduCollect and consolidate GitHub pull request feedback and CI check statuses.