本文へ移動
cccskills
無料GitHub で公開

change-impact-annotate

Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

<!-- implements: DES-assured-skills-006 -->

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

  1. Inspect the diff. Identify the touched files and (best-effort) the touched functions.

  2. Map files to module IDs using programs.yaml.

  3. Map touched functions to cited artefact IDs by parsing existing # implements: annotations.

  4. Compute the next CHG number. Scan docs/change-impacts/CHG-*.md; new ID = max + 1.

  5. 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
  6. Prompt the user to fill in the empty fields. Surface verification approach as the highest-stakes field (this is the regulator's primary check).

  7. Save. Write to docs/change-impacts/CHG-<NNN>.md.

  8. Re-run change_impact_gate to verify the record covers all touched code files.

  9. 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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.

日本語の概要は準備中です。原文の説明を表示しています。

SteveGJones/ai-first-sdlc-practices412026年10月5日 更新

Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.

日本語の概要は準備中です。原文の説明を表示しています。

SteveGJones/ai-first-sdlc-practices412026年10月5日 更新

Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.

日本語の概要は準備中です。原文の説明を表示しています。

SteveGJones/ai-first-sdlc-practices412026年10月5日 更新

Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.

日本語の概要は準備中です。原文の説明を表示しています。

SteveGJones/ai-first-sdlc-practices412026年10月5日 更新

Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.

日本語の概要は準備中です。原文の説明を表示しています。

SteveGJones/ai-first-sdlc-practices412026年10月5日 更新

Generate boilerplate `# implements:` annotation for a function based on the artefact ID, inserting it as the first line of the function body.

日本語の概要は準備中です。原文の説明を表示しています。

SteveGJones/ai-first-sdlc-practices412026年10月5日 更新

SteveGJones のスキルをすべて見る

このスキルの問題を報告する