commit

Archive planning documents, update features.yaml, and commit session work.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill commit-masta-g3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/masta-g3/rules/tree/main/skills/commit
Command: npx skills add https://github.com/masta-g3/rules --skill commit-masta-g3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams finalize work by archiving planning artifacts and cleaning up session traces to keep repositories tidy.

Core Features & Use Cases

  • Archive Planning Document: Moves the planning Markdown to docs/history and creates a durable summary
  • Update features.yaml: If tracked feature, mark as "done" with completed_at today and link the archive plan
  • Repo Docs: Update docs/STRUCTURE.md, README.md, and related guides to reflect finished work with concise edits
  • Commit: Inspect status, stage session files, and create a descriptive commit message for the completed work

Quick Start

Archive the planning file and finalize the session changes with the commit workflow.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate archiving planning documents when finalizing a git commit?

Automating planning document archival moves Markdown files to docs/history and creates a durable summary. This workflow cleans up session traces and keeps repositories tidy before finalizing the commit.

What is the best way to update features.yaml when tracked work is done?

Updating features.yaml marks tracked features as done with today's completed_at date and links the archive plan. This ensures feature status tracking remains accurate across single or multi-repo projects.

How do I include documentation updates in a git commit workflow?

Include documentation updates by editing docs/STRUCTURE.md and README.md to reflect finished work. The workflow then stages these session files alongside planning artifacts for a descriptive commit.

Does this commit workflow support both standalone and feature-driven multi-repo projects?

Yes, the commit workflow applies to both feature-driven and standalone workflows across single or multi-repo projects. It handles planning, review, and commit steps uniformly regardless of project scale.

How do I stage session files and generate a descriptive git commit message?

Stage session files by inspecting git status and staging changes. The workflow then creates a descriptive commit message summarizing the completed work and archival actions for the repository.