speclink-commit

Commit source files and artifacts for a specific Speclink change.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speclink-commit
Source: https://github.com/MomoChenisMe/speclink/tree/main/.agents/skills/speclink-commit
Command: npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, speclink-cli, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of committing files associated with a specific Speclink change, ensuring that only relevant files are committed, saving time and reducing errors.

Core Features & Use Cases

  • Selective Committing: Commit only the files related to a specific Speclink change, including source files and artifacts.
  • User Confirmation: Provides a detailed commit plan and asks for user confirmation before proceeding.
  • Integration with Git: Requires git and integrates seamlessly with the Git workflow.
  • Use Case: Ideal for developers working on multiple changes simultaneously, allowing them to commit changes for a specific feature or bug fix without affecting other work.

Quick Start

Run the speclink-commit command followed by the change name, e.g., speclink-commit add-auth.

Frequently Asked Questions about speclink-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 Speclink change in Git?

To selectively commit Speclink change files, you can use a tool that reads a structured tracking file to identify and commit only the relevant source files and artifacts via Git.

How does selective Git committing work for multiple concurrent feature changes?

Selective Git committing uses a structured tracking file to identify specific source files and artifacts associated with a change, ensuring unrelated work-in-progress files are excluded from the commit.

Do I need Git and Speclink CLI installed to commit Speclink changes?

Yes, you need both Git and Speclink CLI installed, as the selective commit process relies on a functioning Git environment and utilizes Speclink CLI to identify the relevant files.

Can I review the files before committing a Speclink change?

Yes, the process generates a detailed commit plan outlining the specific source files and artifacts to be included, prompting for user confirmation before executing the Git commit.

What is the best way to isolate source file commits when working on multiple Speclink changes?

The best way to isolate commits is to use a selective commit process that references a structured tracking file, ensuring only files mapped to the specific Speclink change are committed.

How to execute a selective commit for a Speclink change?

Run the commit command followed by the change name, which triggers the tool to parse the tracking file, present a commit plan for confirmation, and execute the Git commit for the relevant files.