spectra-commit

Stage and commit only relevant artifacts for a specified Spectra change.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/kaochenlong/handshake --skill spectra-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-commit
Source: https://github.com/kaochenlong/handshake/tree/main/.claude/skills/spectra-commit
Command: npx skills add https://github.com/kaochenlong/handshake --skill spectra-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit only the relevant files for a Spectra change, reducing accidental commits of unrelated work by reading per-change tracking data and artifact lists.

Core Features & Use Cases

  • Reads tracking data to identify source files touched by a change
  • Collects artifact files under openspec/changes/<name>/ for commit
  • Presents a deterministic commit plan with artifact, source, and unrelated sections and prompts for confirmation
  • Supports an optional archive-first flow to move changes into archived storage and include them in the commit
  • Ensures per-file staging (no git add .) and explicit user confirmation before committing

Quick Start

Commit artifacts for a specific Spectra change by selecting tracked files and staging them individually before finalizing the commit.

Frequently Asked Questions about spectra-commit

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

FAQPage Schema
How do I commit only specific Spectra change artifacts without staging unrelated files?

To commit Spectra change artifacts without unrelated files, the skill reads per-change tracking data to identify relevant artifacts and source files, stages them individually, and prompts for explicit confirmation before committing.

What is the best way to track and commit source files touched by a specific workflow change?

Tracking and committing source files touched by a workflow change involves reading per-change tracking data, generating a deterministic commit plan separated into artifact, source, and unrelated sections, and enforcing per-file staging.

Can I archive Spectra changes before committing them to source control?

Yes, you can archive Spectra changes before committing by using the optional archive-first flow, which moves changes into archived storage and includes those archived files in the final commit plan.

How does the commit plan separate artifacts from unrelated working files?

The commit plan separates artifacts from unrelated working files by coordinating tracking data and artifact file selection, presenting a deterministic plan divided into artifact, source, and unrelated sections for explicit user confirmation.

Does this workflow use git add to stage all changes at once?

No, this workflow avoids bulk staging commands like git add by enforcing per-file staging, ensuring only the identified artifact and source files are staged to prevent unintended changes from being committed.