skills.rest
EpicenterHQ
EpicenterHQOFFICIAL
Explore all skills by this author →
Website𝕏@EpicenterHQGitHub

incremental-commits

Plan and execute code changes in dependency-ordered waves for atomic commits.

4.7k|374|Updated Mar 16, 2023
Search Tags:#git#refactoring#commits#best-practices#incremental#waves#code-history
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill incremental-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incremental-commits
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/incremental-commits
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill incremental-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break multi-file changes into atomic commits ordered by dependency, ensuring each commit represents a single logical concern.

Core Features & Use Cases

  • Atomic waves: One logical concern per wave, ensuring a clean, readable git history.
  • Buildable & testable: Each wave results in code that compiles and passes tests, enabling safe integration.
  • Dependency-driven sequencing: Foundation work is committed before dependents, reducing integration friction.
  • Use cases: Ideal for refactors spanning 3+ files, breaking API changes, or feature work across modules.

Quick Start

Plan and execute code changes in waves to keep commits atomic and explainable.

Frequently Asked Questions about incremental-commits

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

FAQPage Schema
How do I split a multi-file refactor into atomic commits?▼

Split a multi-file refactor into atomic commits by planning and executing code changes in waves, keeping each commit focused on a single logical concern for a clean git history.

What is the best way to sequence commits for API-breaking changes?▼

The best way to sequence commits for API-breaking changes is using dependency-driven ordering, ensuring foundational work is committed before dependent code to reduce integration friction.

How do I keep git history readable during a large feature implementation?▼

Keep git history readable during large feature implementations by enforcing wave-based scope, where each wave represents one logical concern and produces explainable commits.

Can I use incremental commits for refactors spanning multiple modules?▼

Yes, incremental commits are ideal for refactors spanning three or more files or multiple modules, breaking down complex multi-file changes into ordered, atomic waves.

Does every commit need to pass tests when making incremental code changes?▼

Yes, every wave of incremental code changes should result in code that compiles and passes tests, ensuring safe integration and buildable commits throughout the refactoring process.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
openeuler-mirroropeneuler-mirror
3

git-master

Generate atomic Git commits and rebase history with forensic search.

Official
Advanced
BarryYinBarryYin

kiro-validate-impl

Validate feature-level integration and cross-task consistency across implemented tasks.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-commit-practices

Enforce Conventional Commits and atomic Git commit practices with Japanese subjects and rationale documentation.

Community
Intermediate