spectra-commit

Automates selective committing of tracked source files and artifacts for a single Spectra change.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Bruno-Yu/portfolio --skill spectra-commit-bruno-yu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-commit
Source: https://github.com/Bruno-Yu/portfolio/tree/main/.cursor/skills/spectra-commit
Command: npx skills add https://github.com/Bruno-Yu/portfolio --skill spectra-commit-bruno-yu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables precise commits for Spectra changes by selecting only artifact and relevant tracked files, avoiding accidental inclusion of unrelated work.

Core Features & Use Cases

  • Selective change commits: Reads tracking data and git status to assemble a focused commit for a single Spectra change.
  • Artifact + source file handling: Stages only change artifacts found under openspec/changes/<name>/ and associated tracked source files when available.
  • Guided workflow: Presents a commit plan, prompts for archiving and syncing steps, and generates a tailored commit message based on the proposal.
  • Use Case: When multiple changes are in flight, this skill ensures you commit the correct subset of changes, keeping history clean.

Quick Start

Run spectra commit and follow prompts to select a change and review the commit plan.

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 the relevant artifacts for a single Spectra change?

To commit only relevant artifacts for a single Spectra change, the skill reads change tracking data and git status to assemble a focused commit. It stages artifacts under openspec/changes/<name>/ and associated tracked source files.

Can I use selective git commits when multiple changes are in flight?

Yes, selective git commits work specifically for multiple changes in flight. The skill applies guardrails and user confirmation to ensure you commit the correct subset of changes, keeping your repository history clean.

What files do I need in my local repository to automate selective commits?

You need git and the local repository to contain openspec/changes/<name> and .spectra/touched/<change-name>.json. These files identify the change artifacts and source files required to automate selective commits.

How does the commit workflow handle archived items and commit messages?

The commit workflow handles archived items and messages by presenting a commit plan and prompting for archiving and syncing steps. It generates a tailored commit message based on the proposal for the Spectra change.

Does this workflow prevent accidental inclusion of unrelated work?

Yes, this workflow prevents accidental inclusion of unrelated work by selecting only change artifacts and relevant tracked source files. It applies guardrails and requires user confirmation before finalizing the commit.