skills.rest
SteveGJones
SteveGJonesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

change-impact-annotate

Generate a CHG-<NNN>.md draft from a git diff for regulated projects.

41|6|Updated Jul 12, 2025
Search Tags:#documentation#compliance#gate#code-change#change-impact#artefacts#regulated-context
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill change-impact-annotate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-impact-annotate
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-assured/skills/change-impact-annotate
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill change-impact-annotate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies touched files and modules from a git diff and generates a structured change-impact record to support regulatory gates.

Core Features & Use Cases

  • Surface affected REQ, DES, TEST, and CODE artefacts from the change.
  • Compute the next CHG- number and draft a record at docs/change-impacts/CHG-<NNN>.md.
  • Validate against the change_impact_gate, populate discovered references, and prompt for missing details before merge.

Quick Start

Review the current git diff and run change-impact-annotate to generate the next CHG-<NNN>.md draft.

Frequently Asked Questions about change-impact-annotate

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

FAQPage Schema
How do I generate a change-impact record from a git diff for a regulated project?▼

To generate a change-impact record, scan the git diff to identify touched files and surface affected REQ, DES, TEST, and CODE artefacts, then draft a structured CHG-<NNN>.md file for the regulatory gate.

What is a change-impact gate and when do I need to document artefacts for compliance?▼

A change-impact gate enforces structured documentation for regulated projects by requiring a CHG-<NNN>.md record that maps touched files to affected REQ, DES, TEST, and CODE artefacts before merge.

How do I trace affected requirements, design, and test artefacts from code changes?▼

Trace affected artefacts by scanning the git diff to automatically surface referenced REQ, DES, TEST, and CODE components and populate them into a structured change-impact compliance draft.

Does the change-impact annotation process work without a regulated context?▼

No, the change-impact annotation process specifically operates on regulated-context projects where the change_impact_gate is enabled to enforce compliance documentation generation.

How do I determine the next CHG- number and populate missing details before merge?▼

The system computes the next CHG- number automatically from existing records, drafts the file from a template, populates discovered references, and prompts for missing details before saving and re-validating against the gate.

Related Skills

Explore More Legal & Compliance Skills→
h-4vokh-4vok

architecture-reviewer

Review changed files or modules against repository engineering principles and rubric.

Community
Advanced
fabioabrfabioabr

adr-writer

Create and update Markdown Architecture Decision Records with validated front matter.

Community
Advanced
SteveGJonesSteveGJones
41

req-link

Validate target IDs in the registry before inserting satisfies links between artefacts.

Community
Intermediate
dividedbydividedby
1

doc-it

Scan local files to patch stale READMEs, API docs, and CHANGELOGs.

Community
Advanced