How do I install the Done skill?

Run npx skillmds@latest add diegosouzapw/done-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Done skill do?

Complete current expedition - run tests, commit, push, and update kanban status It is listed under Security on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Done?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Done by diegosouzapw — Agent Skill

Name: Done
Author: diegosouzapw

File contents

Complete Work

Finish the current expedition: run tests, commit changes, push to remote, and update kanban status.

Steps

1. Identify Current Work

# Check current branch
git branch --show-current

# Check in-progress items
yurtle-kanban list --status in_progress

If $ARGUMENTS provided, use that expedition. Otherwise, infer from branch name or ask.

2. Run Tests

Run appropriate tests based on what was changed:

# Unit tests for modified modules
pytest brain/MODULE/tests/ -v

# Integration tests if applicable
pytest brain/tests/ -v -k "integration"

# Live being tests if applicable (CLI-first)
pytest live-being-tests/test_*.py -v

Report test results. If tests fail, DO NOT proceed - fix issues first.

3. Commit Changes

# Check what's changed
git status
git diff --stat

# Stage and commit with expedition reference
git add -A
git commit -m "feat(exp-XXX): Brief description

- What was implemented
- Key changes

Co-Authored-By: Claude <noreply@anthropic.com>"

4. Push to Remote

git push origin HEAD

4b. Version Check (for significant changes)

If this work adds features or fixes bugs, consider bumping the version:

# Check current version
grep version pyproject.toml | head -1

# For bug fixes: bump patch (1.1.0 → 1.1.1)
# For new features: bump minor (1.1.0 → 1.2.0)
# For breaking changes: bump major (1.1.0 → 2.0.0)

If version bump is appropriate, use /release patch after merging to main.

5. Create PR (required for expedition branches)

Create PR so other agents can see the work is ready for review:

gh pr create --title "feat(exp-XXX): Title" --body "## Summary
- What this PR does

## Test Plan
- How it was tested

## Expedition
EXP-XXX: [Title]"

6. Update Kanban Status

IMPORTANT: This makes the work visible to other agents (e.g., Agent A checking for reviews):

# Move to review (for changes needing review)
yurtle-kanban move EXP-XXX review

# Or if self-contained, fully tested, and ready to merge:
yurtle-kanban move EXP-XXX done

7. Show Next Work

yurtle-kanban list --status ready --limit 3

Suggest the next highest-priority item.

---name: done-2description: Complete current expedition - run tests, commit, push, and update kanban status---# Complete WorkFinish the current expedition: run tests, commit changes, push to remote, and update kanban status.## Steps### 1. Identify Current Work```bash# Check current branchgit branch --show-current# Check in-progress itemsyurtle-kanban list --status in_progress```If $ARGUMENTS provided, use that expedition. Otherwise, infer from branch name or ask.### 2. Run TestsRun appropriate tests based on what was changed:```bash# Unit tests for modified modulespytest brain/MODULE/tests/ -v# Integration tests if applicablepytest brain/tests/ -v -k "integration"# Live being tests if applicable (CLI-first)pytest live-being-tests/test_*.py -v```Report test results. If tests fail, DO NOT proceed - fix issues first.### 3. Commit Changes```bash# Check what's changedgit statusgit diff --stat# Stage and commit with expedition referencegit add -Agit commit -m "feat(exp-XXX): Brief description- What was implemented- Key changesCo-Authored-By: Claude <noreply@anthropic.com>"```### 4. Push to Remote```bashgit push origin HEAD```### 4b. Version Check (for significant changes)If this work adds features or fixes bugs, consider bumping the version:```bash# Check current versiongrep version pyproject.toml | head -1# For bug fixes: bump patch (1.1.0 → 1.1.1)# For new features: bump minor (1.1.0 → 1.2.0)# For breaking changes: bump major (1.1.0 → 2.0.0)```If version bump is appropriate, use `/release patch` after merging to main.### 5. Create PR (required for expedition branches)Create PR so other agents can see the work is ready for review:```bashgh pr create --title "feat(exp-XXX): Title" --body "## Summary- What this PR does## Test Plan- How it was tested## ExpeditionEXP-XXX: [Title]"```### 6. Update Kanban Status**IMPORTANT**: This makes the work visible to other agents (e.g., Agent A checking for reviews):```bash# Move to review (for changes needing review)yurtle-kanban move EXP-XXX review# Or if self-contained, fully tested, and ready to merge:yurtle-kanban move EXP-XXX done```### 7. Show Next Work```bashyurtle-kanban list --status ready --limit 3```Suggest the next highest-priority item.

Frequently asked questions

Done