atomic-commit

Engineering Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Atomic git workflow - validates, commits, pushes, creates PR, and verifies CI with zero-warnings policy. Orchestrates complete c…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Overview”, “Usage”, “Arguments”, “State Machine”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name atomic-commit directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Overview / Usage / Arguments” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Atomic Commit Skill

Atomic workflow: validate → commit → push → PR → verify. All changes committed as single unit with zero warnings policy.

Overview

Orchestrates complete code submission as state machine with 7 phases:

PRE_COMMIT - Validation (quality gate, secrets scan)
COMMIT - Atomic commit creation (conventional format)
PRE_PUSH - Remote sync check
PUSH - Upload to origin
PR_CREATE - Open pull request
VERIFY - Wait for CI checks
REPORT - Success summary

Zero warnings policy: Any warning fails the workflow and triggers rollback.

Usage

# Full workflow
/atomic-commit

# With custom message
/atomic-commit --message "feat(auth): add OAuth2 flow"

# Dry run (validate only)
/atomic-commit --dry-run

# Skip CI verification (emergency)
/atomic-commit --skip-ci

Arguments

Argument	Description	Default
`--message, -m`	Commit message (auto-detect if omitted)	auto
`--dry-run`	Validate only, no commits/pushes	false
`--skip-ci`	Skip CI verification	false
`--timeout`	CI wait timeout in seconds	1800
`--base-branch`	Target branch for PR	main

State Machine

[Start] → PRE_COMMIT → COMMIT → PRE_PUSH → PUSH → PR_CREATE → VERIFY → REPORT → [Success]
              ↓           ↓         ↓         ↓          ↓         ↓
            [Fail]      Rollback  Rollback  Rollback   Rollback  Rollback

Quality Gates

Phase	Check	Failure Action
PRE_COMMIT	Quality gate zero warnings	Abort
PRE_COMMIT	No secrets in diff	Abort
PRE_COMMIT	Not on protected branch	Abort
COMMIT	Valid conventional format	Rollback
PRE_PUSH	Remote accessible	Rollback
PUSH	SHA verification	Rollback
PR_CREATE	gh CLI authenticated	Rollback
VERIFY	All CI checks green	Rollback
VERIFY	Zero warnings in checks	Rollback

Rollback Actions

On failure, automatically:

Close PR (if created)
Remove remote commit (best effort)
Reset local commit
Unstage changes

Error Codes

Code	Meaning
0	Success
2	Quality gate failed
3	Commit failed
4	Push failed
5	PR creation failed
6	Checks failed/warnings found
7	Timeout
8	Rollback failed

Prerequisites

gh CLI installed and authenticated
Working on feature branch (not main/master)
./scripts/quality_gate.sh exists

Configuration

Environment variables:

ATOMIC_COMMIT_TIMEOUT=1800          # Check wait timeout
ATOMIC_COMMIT_BASE_BRANCH=main      # Target branch for PR
ATOMIC_COMMIT_NO_ROLLBACK=0         # Set 1 to disable rollback

Commit Format

type(scope): Brief description (50 chars max)

- Why (not what) - user perspective
- Reference issues: Fixes #123

Types: feat, fix, docs, style, refactor, perf, test, ci, chore

Implementation

This skill uses sub-agents for each phase:

validate - Phase 1: PRE_COMMIT
commit - Phase 2: COMMIT
push - Phases 3-4: PRE_PUSH & PUSH
create-pr - Phase 5: PR_CREATE
verify - Phase 6: VERIFY

Success Criteria

Command succeeds only when:

✓ All local validation passes (zero warnings)
✓ Commit created with valid SHA
✓ Pushed to remote successfully
✓ PR created with valid URL
✓ All GitHub Actions pass
✓ Zero warnings in all checks

Test change

Source: d-oit/do-knowledge-studio — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Env read
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview atomic-commit.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Atomic Commit Skill

Atomic workflow: validate → commit → push → PR → verify. All changes committed as single unit with **zero warnings** policy.

## Overview

Orchestrates complete code submission as state machine with 7 phases:
1. PRE_COMMIT - Validation (quality gate, secrets scan)
2. COMMIT - Atomic commit creation (conventional format)
3. PRE_PUSH - Remote sync check
4. PUSH - Upload to origin
5. PR_CREATE - Open pull request
6. VERIFY - Wait for CI checks
7. REPORT - Success summary

**Zero warnings policy**: Any warning fails the workflow and triggers rollback.

## Usage

```bash
# Full workflow
/atomic-commit

# With custom message
/atomic-commit --message "feat(auth): add OAuth2 flow"

# Dry run (validate only)
/atomic-commit --dry-run

# Skip CI verification (emergency)
/atomic-commit --skip-ci
```

## Arguments

| Argument | Description | Default |
|----------|-------------|---------|
| `--message, -m` | Commit message (auto-detect if omitted) | auto |
| `--dry-run` | Validate only, no commits/pushes | false |
| `--skip-ci` | Skip CI verification | false |
| `--timeout` | CI wait timeout in seconds | 1800 |
| `--base-branch` | Target branch for PR | main |

## State Machine

```
[Start] → PRE_COMMIT → COMMIT → PRE_PUSH → PUSH → PR_CREATE → VERIFY → REPORT → [Success]
              ↓           ↓         ↓         ↓          ↓         ↓
            [Fail]      Rollback  Rollback  Rollback   Rollback  Rollback
```

## Quality Gates

| Phase | Check | Failure Action |
|-------|-------|----------------|
| PRE_COMMIT | Quality gate zero warnings | Abort |
| PRE_COMMIT | No secrets in diff | Abort |
| PRE_COMMIT | Not on protected branch | Abort |
| COMMIT | Valid conventional format | Rollback |
| PRE_PUSH | Remote accessible | Rollback |

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Overview → Usage → Arguments → State Machine → Quality Gates → Rollback Actions
terms    -> zero warnings · Zero warnings policy · Types · Atomic workflow: validate → commit → push → PR → verify. · Orchestrates complete code submission as state machine with 7 phases: 1. · Zero warnings policy: Any warning fails the workflow and triggers rollback. · On failure, automatically: 1. · Command succeeds only when: 1.
files/cmd -> --message, -m · --dry-run · --skip-ci · --timeout · --base-branch · ./scripts/qualitygate.sh · validate · commit
body sha256 -> ae4d62d291a3