atomic commit
- Repo stars 0
- Author repo skills-registry
- Domain
- 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
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Env read
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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 |
| 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:
1. Close PR (if created)
2. Remove remote commit (best effort)
3. Reset local commit
4. 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:
```bash
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:
1. ✓ All local validation passes (zero warnings)
2. ✓ Commit created with valid SHA
3. ✓ Pushed to remote successfully
4. ✓ PR created with valid URL
5. ✓ All GitHub Actions pass
6. ✓ Zero warnings in all checks
## See Also
- `.opencode/commands/commit.md` - Basic commit guidelines
- `.github/PULL_REQUEST_TEMPLATE.md` - PR template
- `references/IMPLEMENTATION.md` - Technical details
# Test change
---
> Source: [d-oit/do-knowledge-studio](https://github.com/d-oit/do-knowledge-studio) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Sections and files
Listed in source order.
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/quality_gate.sh · validate · commit
body sha256 -> ae4d62d291a3
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
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 · 1800Quality 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
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