address

Fixes findings from CI-posted pull request reviews and pushes the commit to the PR branch.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/matthewalton/speccle --skill address-matthewalton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address
Source: https://github.com/matthewalton/speccle/tree/main/packages/plugin/skills/address
Command: npx skills add https://github.com/matthewalton/speccle --skill address-matthewalton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After CI posts an automated review on a pull request, someone still has to read the findings, decide whether they can be fixed autonomously, apply the fixes safely, and close the loop on the PR branch. This Skill automates that entire post-review workflow with a deterministic risk gate deciding whether a human is required. ## Core Features & Use Cases - Posted-review consumption: Reads the latest CI-posted review findings via speccle review findings, resolving the pull request automatically from the current branch with gh pr view. - Risk-gated fixing: Computes a deterministic risk score with oracle risk; below the threshold it fixes findings autonomously, re-running the checks-gate after each fix and reverting any fix that goes red. - Closed-loop landing: Records calibration data, routes each finding to a durable remedy (check, criterion, or lens), lands surviving fixes in one commit, and pushes it to the pull request's branch. - Use Case: A developer returns to a PR where CI posted review findings overnight. They ask the agent to "address the review", and the skill verifies the tree matches the reviewed head, fixes the low-risk findings, pushes the commit, and summarizes every finding's outcome. ## Quick Start Ask the agent to address the review findings on the pull request for the current branch.

Frequently Asked Questions about address

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix review findings posted on a pull request?▼

Run the address skill on the PR's branch. It reads the latest CI-posted review with `speccle review findings`, computes a risk score, fixes findings below the threshold while re-running the checks-gate after each fix, and pushes one commit to the PR branch.

What is the difference between the review and address skills?▼

The review skill derives findings locally by fanning a panel of lenses over the pending change and never pushes. The address skill acts on findings CI already posted on a pull request and always pushes its fix commit to the PR branch.

What happens if there is no posted review on the pull request?▼

The skill stops and reports that no review was posted. It does not run a local panel as a substitute; instead it suggests waiting for CI or running the review skill for a locally derived panel.

Can the skill fix findings when the risk score is above the threshold?▼

No. When the deterministic risk score meets or exceeds the review threshold, or the risk lens escalates, a human is required. The skill reports every finding with a proposed remedy but fixes nothing.

What happens when a fix fails the checks-gate?▼

The fix is reverted to its pre-fix state rather than patched around, and the finding is carried forward as unfixed in the summary. Only reds caused by the fix itself trigger a revert; pre-existing reds on unrelated criteria do not.

Does the address skill work when the local branch differs from the reviewed commit?▼

No. It compares `git rev-parse HEAD` with the review's headSha and stops if they differ, since pushing from a diverged tree would carry work no lens reviewed. Pulling, pushing, or switching branches is left to the human.