What is change-impact-annotate?

A guided record of how a code change affects requirements, designs, tests, source code, and modules in projects subject to standards such as IEC 62304, FDA rules, or ISO 26262.

Use it before submitting a covered change to identify affected records, capture its effects and verification method, and run the project’s change check.

It creates the change documentation needed when regulated-project checks require evidence of affected areas and human review.

change-impact-annotate — Skill for Claude Code by SteveGJones

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add SteveGJones/ai-first-sdlc-practices --skill change-impact-annotate

Clone the repo

git clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practices

Made for: Claude Code.

Or install sdlc-assured, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/change-impact-annotate/github.svg)](https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/change-impact-annotate)

Your own site

<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/change-impact-annotate"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/change-impact-annotate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/change-impact-annotate"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/change-impact-annotate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 439 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.00439
Opus 5	$0.00028	$0.00219
Sonnet 5	$0.00011	$0.00088
Haiku 4.5	$0.00006	$0.00044

Measured 10d ago against content hash 885ae4b848f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

change-impact-annotate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/sdlc-assured/skills/change-impact-annotate/SKILL.md · 43 lines

What it actually says

Skill: change-impact-annotate

Use this skill before pushing a code change that touches a regulated-context project where change_impact_gate is enabled. Produces a docs/change-impacts/CHG-NNN.md record that satisfies the gate.

Inputs

The unstaged or just-staged code changes (read from git diff)

Steps

Inspect the diff. Identify the touched files and (best-effort) the touched functions.
Map files to module IDs using programs.yaml.
Map touched functions to cited artefact IDs by parsing existing # implements: annotations.
Compute the next CHG number. Scan docs/change-impacts/CHG-*.md; new ID = max + 1.
Generate a draft. Use the change-impact.md template, pre-filled with:
- Discovered REQs, DESs, TESTs, code locations, modules
- Empty fields for: change summary, downstream effects, verification approach, approver
Prompt the user to fill in the empty fields. Surface verification approach as the highest-stakes field (this is the regulator's primary check).
Save. Write to docs/change-impacts/CHG-<NNN>.md.
Re-run change_impact_gate to verify the record covers all touched code files.
Remind. "Approval signature is required before merge — the framework records it; the human authorises it."

Done criteria

CHG-<NNN>.md written.
All touched code files cited in the record.
change_impact_gate passes.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 43 lines · 55 tokens per session scan A 885ae4b848f9

Subscribe to this mod's changes

change-impact-annotate is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 439 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Legal and compliance Planning

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens