spectra-commit

Stage and commit files for a specific Spectra change from a manifest.

Updated Mar 26, 2024
One-click install
npx skills add https://github.com/SHUSHU010829/shushu.tw --skill spectra-commit-shushu010829
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-commit
Source: https://github.com/SHUSHU010829/shushu.tw/tree/main/.claude/skills/spectra-commit
Command: npx skills add https://github.com/SHUSHU010829/shushu.tw --skill spectra-commit-shushu010829

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates selective commits for a specific Spectra change, ensuring only artifacts and required source files are committed while excluding unrelated work.

Core Features & Use Cases

  • Select Change: identify the target change by name or context.
  • Artifact aware: includes only files under openspec/changes/<name>/ and any tracked artifacts.
  • Safe commit flow: requires explicit user confirmation for included files and provides a full commit plan.

Quick Start

Provide the change name and confirm the commit plan to start committing the correct files.

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 files related to a specific change while excluding unrelated work?

Selective commits isolate change-specific files by parsing a manifest and git status to include only relevant artifacts and tracked source files. This ensures unrelated work-in-progress stays unstaged while committing the target change.

What is a Spectra change manifest and how does it automate git staging?

A Spectra change manifest defines the artifacts tied to a specific change under openspec/changes/<name>/. The automation parses this manifest to identify and stage only the files belonging to that change, preventing unrelated files from entering the commit.

How to safely stage tracked source files alongside artifact directories in git?

Safe staging requires explicit user confirmation for each included file. The workflow prompts for approval before staging any tracked source files or artifacts, providing a full commit plan to prevent accidentally committing unrelated code.

Does git selective commit work when I have multiple active changes in my repository?

Yes, selective commit workflows parse the git status to identify files for a specific change. They infer the target change name from context and actively report unrelated changes found in the working directory without staging them.

How do I start a selective commit for a specific change name?

Provide the target change name to initiate the selective commit flow. The automation collects the corresponding artifact files, optionally adds tracked source files, and presents a commit plan for your explicit confirmation before staging.