vcsdd git integration

Engineering Community

Skill notes

When to Activate

Running /vcsdd-commit command Creating phase-completion commits Tagging pipeline milestones

Atomic Staging

Stage all VCSDD artifacts atomically: Only stage files that belong to the active feature and current phase. If unrelated dirty files exist, stop and require a manual review instead of widening the stage set.

Auto-Commit Safety Rules

Auto-commit (VCSDD_AUTO_COMMIT=true) refuses to commit if: Unrelated dirty files exist in worktree Phase transition is invalid No phase change detected since last commit

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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
@sc30gsw · 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
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# VCSDD Git Integration

## When to Activate
- Running /vcsdd-commit command
- Creating phase-completion commits
- Tagging pipeline milestones

## Commit Message Format

```
vcsdd(<phase>): <feature-name> - <phase-description>

Phase: <phase-id>
Feature: <feature-name>
Sprint: <N>
Gate: <PASS|FAIL|SKIP>
Beads: <bead-ids-affected>
Iteration: <N>

Artifacts:
- specs/behavioral-spec.md [modified]
- evidence/sprint-1-red-phase.log [added]

Traceability:
- REQ-001 -> TEST-001 -> IMPL-001 [green]
- REQ-002 -> TEST-002 [red, pending implementation]
```

## Git Tag Format

```
vcsdd/<feature>/phase-1a    # Spec crystallization complete
vcsdd/<feature>/phase-1c    # Spec gate passed
vcsdd/<feature>/phase-2a    # Red phase complete
vcsdd/<feature>/phase-2b    # Green phase complete
vcsdd/<feature>/phase-3-i1  # Adversary review iteration 1
vcsdd/<feature>/phase-6     # Convergence achieved
```

## Atomic Staging

Stage all VCSDD artifacts atomically:
```bash
git add -- .vcsdd/index.json .vcsdd/history.jsonl .vcsdd/active-feature.txt .vcsdd/features/<name>/ [phase-scoped source/test/spec files]
git commit -m "vcsdd(2b): my-feature - implementation (green phase)"
git tag vcsdd/my-feature/phase-2b
```

Only stage files that belong to the active feature and current phase. If unrelated dirty files exist, stop and require a manual review instead of widening the stage set.

## Auto-Commit Safety Rules

Auto-commit (VCSDD_AUTO_COMMIT=true) refuses to commit if:
- Unrelated dirty files exist in worktree
- Phase transition is invalid
- No phase change detected since last commit

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.