Skip to content
Back to skills

Done

ASecurity

Complete current expedition - run tests, commit, push, and update kanban status

  • 57 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
testingpythonbashgit

Works with

  • cli

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill done --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Done?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Done
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-done/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-done)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: done
description: Complete current expedition - run tests, commit, push, and update kanban status
disable-model-invocation: true
allowed-tools: Bash(yurtle-kanban *), Bash(git *), Bash(pytest *), Bash(python3 *), Bash(gh *)
argument-hint: "[EXP-XXX]"
---

# Complete Work

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

## Steps

### 1. Identify Current Work

```bash
# 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:

```bash
# 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

```bash
# 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

```bash
git push origin HEAD
```

### 4b. Version Check (for significant changes)

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

```bash
# 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:

```bash
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):

```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

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

Suggest the next highest-priority item.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.