AgentStack
SKILL verified Apache-2.0 Self-run

Deepdone Commit

skill-lakesoftai-deepdone-agent-skills-deepdone-commit · by lakesoftai

Prepare or create a safe focused git commit for completed DeepDone work after ledger, verification, and review gates pass. Use when the user asks for a commit candidate, asks to commit, or a supervisor mode authorizes commit.

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-lakesoftai-deepdone-agent-skills-deepdone-commit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Deepdone Commit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

DeepDone Commit

Purpose

Prepare or create a focused git commit for completed DeepDone work.

This is a safety gate, not a formatting helper.

Default behavior is commit candidate only when intent is unclear. Commit automatically when the current request or supervisor context asks for commit, uses commit mode, or comes from until-commit/end-to-end.

Do not ask for permission to commit. Either commit after gates pass, or stop with exact blockers.

Never push.

Inputs

The user may ask for:

  • commit candidate only,
  • actual commit,
  • commit message draft,
  • staging plan.

If unclear, prepare candidate only.

Treat these as commit authorization for the current run:

  • direct user request to commit,
  • supervisor classification ready_to_commit,
  • mode until-commit,
  • mode end-to-end,
  • a child-skill prompt that says commit mode.

Treat these as commit denial:

  • do not commit,
  • candidate only,
  • commit candidate only,
  • prepare only.

Preconditions

Before preparing a commit candidate, inspect:

  • git status --short --untracked-files=all,
  • git diff --stat,
  • active roadmap if present,
  • active epic ledger,
  • latest Verification Log,
  • latest structured review result (review-result: pass|fail|blocked),
  • Open Loops,
  • AGENTS instructions.

Before actual commit, all must be true:

  • commit is authorized by current request or supervisor context,
  • no .deepdone/STOP file exists,
  • changed files are expected,
  • active ledger is current,
  • verification entries include result: pass|fail|blocked, and no failed or blocked check remains unaccepted,
  • review has no blocking findings,
  • no unresolved Open Loop blocks this commit,
  • commit message accurately describes the diff,
  • no dangerous files are included.

Dangerous Files

Do not commit files that appear to contain secrets or local-only state unless the user explicitly approves and the repo policy allows it.

Examples:

  • .env
  • .env.*
  • secret files
  • private keys
  • credentials
  • tokens
  • local database dumps
  • generated build artifacts not normally committed
  • .deepdone/commit-candidate.md
  • local agent, editor, or orchestration scratch files

Commit Harness

If available, use:

python3 scripts/commit_progress.py --candidate

For an actual commit, use the harness when commit is authorized:

python3 scripts/commit_progress.py --commit --yes

Do not run git add ..

The harness stages exact files intentionally, including expected untracked files. It must not create repo-local candidate files by default. Candidate output should go to stdout unless the user explicitly asks for a file.

If the bundled harness is not available, use normal git commands directly:

  1. inspect git status --short --untracked-files=all,
  2. reject dangerous or local-only paths,
  3. stage exact expected paths with git add -- ...,
  4. commit with git commit -F or git commit -m,
  5. report hash.

If the environment refuses writes to .git/index, .git/HEAD, or refs, report that as an environment permission blocker. Do not fall back to writing git internals manually.

Workflow

  1. Inspect current git and DeepDone state.
  2. Confirm commit eligibility.
  3. If not eligible, stop and explain exact missing gate.
  4. Prepare a candidate with:
  • summary,
  • files to stage,
  • verification evidence,
  • review evidence,
  • residual risk,
  • commit message.
  1. If user asked only for candidate, stop.
  2. If commit is authorized, stage exact files and commit.
  3. Report commit hash if created.
  4. Never push.

Commit Message Format

Use:

: 

DeepDone:
- Epic: 
- Milestone: 
- Verification:
  - : 
- Review:
  - 

Keep the subject under 72 characters when practical.

Output

Return:

  • candidate or commit result,
  • files included,
  • files excluded,
  • checks considered,
  • review gate status,
  • commit message,
  • next action.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.