component-sync-specs
Ensure a component implementation is synchronized with its specifications.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 3
- Forks
- 4
01 前言 Front Matter
- name
- component-sync-specs
- description
- Ensure a component implementation is synchronized with its specifications.
- argument-hint
- [component-name, component-name, ...]
03 SKILL.md 正文
Work hard and think hard about this task. Spec-sync demands careful, thorough analysis: verify every FR/SC against the actual implementation, corroborate each drift finding with concrete file:line evidence, and never rubber-stamp. Do not rush — reason deeply about each discrepancy before proposing a change.
For each component identified in $ARGUMENTS, run the following:
- /speckit-sync-analyze
- /speckit-sync-propose --interactive
- /speckit-sync-apply
- Stamp the drift report for the CI Spec-Sync Gate.
Step 4 — Stamp the drift report
The CI Spec-Sync Gate (see Jenkinsfile) does not run Claude. It trusts a
freshness stamp that this step writes into each component's committed
drift-report.md. Perform it for every component after its sync is applied.
For a component whose directory is <dir> (e.g. components/memory-tier,
lib/component-framework, benchmarks/rdma-test):
-
Compute the input hash over the component's
src/+specs/(withcomponents/interfaces/folded in), using the committed helper so the value matches what CI will recompute:scripts/spec-sync-hash.sh <dir> -
Decide
drift_status:clean— no actionable spec/implementation drift remains after apply (doc-only or cosmetic notes in the body are fine).drift— actionable drift is still unresolved. Never stampcleanto get a PR through the gate; fix the drift or leave itdriftand explain.
-
Write these flat keys as YAML frontmatter at the very top of
<dir>/.specify/sync/drift-report.md, preserving the existing human-readable report body below the closing---. Flat, prefixed keys are deliberate so CI can parse them withgrepand no YAML parser. Replace an existingspec_sync_*frontmatter block in place rather than adding a second one:--- spec_sync_component: <component-name> spec_sync_drift_status: clean spec_sync_synced_at: <UTC ISO-8601, e.g. 2026-08-31T14:03:00Z> spec_sync_git_commit: <output of `git rev-parse --short HEAD`> spec_sync_inputs_sha256: <digest from step 1> spec_sync_hash_tool: scripts/spec-sync-hash.sh --- # Drift Report: <component-name> ... existing body ...
Commit the updated drift-report.md together with the code and spec changes so
the stamp travels in the same commit as the inputs it certifies. If you edit any
src/ or specs/ file after stamping, re-run step 1 and update the digest —
otherwise CI will reject the report as stale.
04 同仓库更多 Skills
tools-spin-sync
Synchronize Spin/Promela models with current source code and re-verify
tools-spin-model
Create a new Spin/Promela formal verification model for a system property
tools-creusot-install
Install the Creusot Rust verification tool
tools-creusot-init
Prepare an existing Cargo project to use Creusot formal verification
tools-creusot-coq-install
Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge
tools-creusot-annotate-interfaces
Formally verify a component's properties with Creusot and annotate its interface definitions