skills.rest
derickdsouza
derickdsouzaCOMMUNITY
Explore all skills by this author →
Website𝕏@dsouzaderickGitHub

atomic-execution

Create atomic commits with per-file staging and TDD verification.

Updated Aug 23, 2026
Search Tags:#tdd#verification#code-quality#atomic-commits#git-workflow#version-control#task-isolation
One-click install
npx skills add https://github.com/derickdsouza/dd-claude --skill atomic-execution
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atomic-execution
Source: https://github.com/derickdsouza/dd-claude/tree/main/skills/atomic-execution
Command: npx skills add https://github.com/derickdsouza/dd-claude --skill atomic-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disciplined atomic execution eliminates the inefficiency and risk of bulk commits by enforcing one logical unit of work per commit, paired with a self-verification flow.

Core Features & Use Cases

  • Per-task commits: after each task, commit immediately with verification.
  • Granular staging: stage files individually rather than using git add . or git add -A.
  • Clear commit taxonomy: use feat, fix, test, refactor, or chore for each commit.
  • TDD-driven workflow: write tests, observe red, green, and refactor steps with recorded outcomes.
  • Audit-ready logs: record commit hashes and verification results for traceability.

Quick Start

Follow the workflow to complete a task, stage changes by file, and commit a single logical unit after verification.

Frequently Asked Questions about atomic-execution

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

FAQPage Schema
How do I enforce atomic commits in my git workflow?▼

Atomic commits require staging files individually and committing one logical unit per task. You must verify each change using a TDD flow before committing with deterministic types like feat, fix, test, refactor, or chore.

What is the best way to track TDD verification results for audit trails?▼

Tracking TDD verification results involves recording red, green, and refactor outcomes alongside commit hashes. This creates audit-ready logs that map each verifiable change to its specific task and recorded test status.

How do I stop using bulk commits and stage files individually in git?▼

To stop bulk commits, avoid using git add . or git add -A. Instead, stage files individually using per-file staging commands, ensuring each commit represents a single logical unit of work.

Does atomic execution work with standard commit types like feat and fix?▼

Atomic execution enforces deterministic commit types including feat, fix, test, refactor, and chore. Each task must be classified under one of these categories before committing the logical unit.

Why should I commit one logical unit per task instead of batching changes?▼

Committing one logical unit per task eliminates the risk of half-done work by ensuring every change is traceable and verifiable. This disciplined approach replaces bulk commits with audit-ready records of individual features or fixes.

Can I apply atomic commits to refactoring tasks?▼

Atomic commits apply to refactoring tasks by isolating the refactor as a single logical unit. You stage the modified files individually, run TDD verification, and commit using the refactor type to maintain traceability.

Related Skills

Explore More Software Engineering Skills→
hbvg234hbvg234
1

tdd

Automate RED→GREEN→REFACTOR cycles with multi-agent context isolation.

Community
Advanced
skwuwuskwuwu

gvm_audit

Verify GVM audit log integrity and export compliance reports.

Community
Intermediate
gautam-achieveaigautam-achieveai
2

clean-builds

Automates code quality tools and package version validation in .NET projects.

Community
Advanced
paulnsorensenpaulnsorensen
2

commit

Stage specific files and create conventional commits in Git.

Community
Intermediate