spectra-commit

To commit only relevant change files, this Skill reads per-change tracking data and collects artifact files under openspec/changes to prepare focused commits. It displays a plan separating change artifacts, source files, and unrelated changes, requiring explicit confirmation before staging.

Preventing mixed changes in your git commit history is achieved by enforcing per-file staging without git add. This Skill surfaces unrelated changes for awareness and stages only selected artifacts and optional tracked source files, ensuring a clean, reproducible history.

Yes, you can archive Spectra changes before committing through an optional Archive-then-Commit flow. This archives changes, updates the commit set, and regenerates the plan to produce a clean, reproducible commit history.

Yes, the commit workflow generates a tailored commit message from the proposal. It counts completed tasks and enforces per-file staging to ensure the commit message accurately reflects the specific change artifacts being submitted.

The best way to manage artifact-scoped commits is using a disciplined workflow that selects relevant files and guides user confirmation. This ensures only change artifacts and optional tracked source files are committed, reducing review effort and maintaining reproducibility.

You should avoid git add . because it stages all modifications indiscriminately, leading to mixed changes. This Skill enforces per-file staging to precisely select relevant artifact files, preventing unrelated changes from entering the commit history.