spectra-commit

Name: spectra-commit
Availability: InStock
Author: Sean

Coordinate and commit files for a single Spectra change with per-file staging.

Updated Apr 21, 2026

Search Tags:#automation #git #workflow #commit #artifact #tracking #spectra

Ready to run

npx skills add https://github.com/SeanChenR/ghibli --skill spectra-commit-seanchenr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spectra-commit
Source: https://github.com/SeanChenR/ghibli/tree/main/.claude/skills/spectra-commit
Command: npx skills add https://github.com/SeanChenR/ghibli --skill spectra-commit-seanchenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Committing files for a single Spectra change while keeping unrelated work separate and ensuring source-tracked artifacts are handled correctly.

Core Features & Use Cases

Select and isolate artifact files for a given change, read tracking data, and identify unrelated dirty files.
Generate an explicit commit plan, offer a change- and task-aware commit workflow (including optional archive flow), and produce a structured commit message.
Supports per-file staging and visible confirmation before committing, ensuring traceability and reproducibility.

Quick Start

Run spectra commit for the active change using the artifact tracking data.

Frequently Asked Questions about spectra-commit

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

FAQPage Schema

How do I isolate and commit only the files for a single change while ignoring unrelated modifications?▼

To isolate a single change for a commit, you parse artifact tracking data to select specific files, detect unrelated dirty files, and enforce explicit per-file staging before finalizing the commit.

How do I generate a structured commit message from task progress and proposal data?▼

Generating a change-aware commit message involves extracting context from the proposal and task progress, then formatting it into a structured message to ensure traceability for the artifact commit.

What is the best way to handle source-tracked artifacts during a git workflow commit?▼

Handling source-tracked artifacts during a git workflow commit requires parsing tracking data, collecting the artifact files, and presenting an explicit commit plan that isolates them from unrelated modifications.

Can I archive artifact files before finalizing a git commit for a specific change?▼

Yes, you can archive artifact files before finalizing the git commit by triggering an optional archive sub-flow that runs after presenting the commit plan and before executing the final commit.

How do I ensure reproducibility when staging files for an automated commit?▼

To ensure reproducibility when staging files for an automated commit, the workflow requires visible confirmation of an explicit per-file staging plan, preventing accidental inclusion of unrelated dirty files.