spectra-commit

Stage and commit files for a specific Spectra CLI change.

1|Updated Dec 7, 2025

Search Tags:#automation #git #workflow #version control #commit #spectra

Ready to run

npx skills add https://github.com/chenwei791129/rancher-kubeconfig-updater --skill spectra-commit-chenwei791129

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spectra-commit
Source: https://github.com/chenwei791129/rancher-kubeconfig-updater/tree/main/.claude/skills/spectra-commit
Command: npx skills add https://github.com/chenwei791129/rancher-kubeconfig-updater --skill spectra-commit-chenwei791129

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

This skill solves the complexity of managing multiple concurrent changes in a single repository by automating the staging and committing of files specific to a single Spectra change.

Core Features & Use Cases

Context-Aware Staging: Automatically identifies and groups artifact files and tracked source files for a specific change.
Archive Integration: Optionally triggers the archive workflow, including task completion and spec syncing, before committing.
Safety-First Workflow: Provides a clear commit plan and requires explicit user confirmation before staging or committing any files.

Quick Start

Ask the assistant to commit the files associated with the add-auth change using the spectra-commit skill.

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 files for a specific change in git without staging unrelated work?▼

Selective staging isolates files associated with a specific development change tracked by the Spectra CLI, grouping artifact and source files together for a clean git commit without staging unrelated concurrent work.

What is the best way to automate git commits for multiple concurrent changes in a single repository?▼

Automating git commits for multiple changes requires context-aware staging that identifies specific artifact and tracked source files, providing an explicit commit plan and requiring user confirmation before executing version control operations.

How do I archive tasks and sync specs before committing source code changes?▼

Archiving tasks and syncing specs occurs through an integrated archive sub-flow that optionally triggers task completion and spec syncing automatically before staging and committing the associated source files to version control.

Does selective staging work with my existing git workflow and directory structure?▼

Selective staging requires the git dependency for version control operations and strict adherence to the Spectra directory structure to successfully identify and track files associated with specific development changes.

How do I safely review files before committing them to version control?▼

To safely review files before committing, the workflow generates a clear commit plan detailing the grouped artifact and source files, then requires explicit user confirmation before proceeding with any staging or committing operations.