Stage and commit files scoped to a selected Spectra change.
npx skills add https://github.com/zooroy/appt-system --skill spectra-commit-zooroy
Please help me install this Agent Skill. Skill: spectra-commit Source: https://github.com/zooroy/appt-system/tree/main/.agents/skills/spectra-commit Command: npx skills add https://github.com/zooroy/appt-system --skill spectra-commit-zooroy
It prevents accidentally committing unrelated changes when you have multiple Spectra changes in progress by staging and committing only the artifacts (and optionally tracked source files) that belong to a specific Spectra change.
Use spectra-commit with a specific change name like: run $spectra-commit add-auth to preview and confirm a commit that includes only that change’s artifacts (and any tracked source files).
High-intent search queries and answers about installing and using this skill.
To commit only specific change files without mixing unrelated dirty files, you can stage artifacts and tracked source files filtered by a specific change name. This prevents accidentally committing unrelated work when multiple changes are active in your git working tree.
You group source files by task during a git commit by reading tracking data from a .spectra/touched/<change-name>.json file. This tracking file maps task-scoped source files to their specific change for accurate staging.
The best way to commit Spectra change artifacts without untracked source code is to collect files under openspec/changes/<name>/ from your git status. This isolates change artifacts and filters out unrelated dirty files from the commit.
Git status alone does not separate change artifacts from unrelated dirty files. You need a staging mechanism that filters your working tree using openspec/changes/<name>/ directories and .spectra/touched tracking data to include only task-scoped files.
Yes, you can generate a structured git commit message by reading openspec/changes/<name>/proposal.md and task completion state. This automatically builds a descriptive commit message based on the specific change's proposal details.
You review a commit plan before staging files in git by using a confirmation gate. This allows you to commit the plan as shown, include all dirty files, customize the file set, or run an archive and sync operation before committing.
Bruno-YuAutomates selective committing of tracked source files and artifacts for a single Spectra change.
lz-freedomVerify change artifacts for completeness, correctness, and coherence before archiving.
mendixApply OpenSpec changes through guided task execution and progress tracking.
yoshihiko555Stage and commit only files discussed in the conversation.
