chunk-commit

Automate conventional Git commits for chunk workflows with required artifacts.

3|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chunk-commit
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/chunk-commit
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the disciplined creation of conventional git commits for chunk work, ensuring documentation and code changes are properly captured.

Core Features & Use Cases

  • Enforces conventional commit format for chunk workflows.
  • Groups chunk artifacts (docs, code, tests) into a single, traceable commit.
  • Guides users to include updated docs/trunk references and source changes in the commit.

Quick Start

Run the chunk-commit command after completing a chunk to generate a conventional commit that includes all updated artifacts.

Frequently Asked Questions about chunk-commit

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

FAQPage Schema
How do I create conventional commits that include both documentation and source code changes?

Creating conventional commits with grouped changes requires aggregating documentation and source files into a single traceable commit. This ensures mandatory artifacts like GOAL.md and tests are validated before committing.

What is a chunk workflow in Git and how does it relate to conventional commits?

A chunk workflow tracks lifecycle artifacts from planning documents like GOAL.md to source code and tests. Conventional commits format these grouped artifacts, ensuring each development chunk is traceable and documented.

How do I automate grouping documentation and tests into a single Git commit?

Automating Git commit grouping requires aggregating updated docs and source changes across the chunk lifecycle. This enforces conventional commit format and validates mandatory artifacts before recording the commit.

Does this conventional commit workflow require any external dependencies or Git plugins?

This conventional commit workflow operates in standard Git environments without external dependencies or plugins. It directly assembles and records commits using the existing Git workflow.

Can I use conventional commit automation for chunk workflows that only involve code changes?

Using conventional commit automation for code-only chunk workflows is possible, but the tool is designed to group documentation and source changes together. It specifically guides users to include updated trunk references and docs in the commit.

Why should I group chunk artifacts into one commit instead of making separate commits for docs and code?

Grouping chunk artifacts into one commit ensures full traceability across the chunk lifecycle, linking planning docs like PLAN.md directly to source and test changes. This maintains a clean conventional commit history with properly captured context.