done

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

16 stars

Best use case

done is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using done should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/done/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/testing-security/done/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/done/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How done Compares

Feature / AgentdoneStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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.

Related Skills

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

Load Test Designer

16
from diegosouzapw/awesome-omni-skill

Design load tests with realistic workload models and performance criteria

ln-634-test-coverage-auditor

16
from diegosouzapw/awesome-omni-skill

Coverage Gaps audit worker (L3). Identifies missing tests for critical paths (Money 20+, Security 20+, Data Integrity 15+, Core Flows 15+). Returns list of untested critical business logic with priority justification.

ln-523-auto-test-planner

16
from diegosouzapw/awesome-omni-skill

Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Calculates priorities, delegates to ln-301-task-creator. Worker for ln-520.

legal-compliance-agent

16
from diegosouzapw/awesome-omni-skill

Generate legally compliant privacy policies, terms of service, HIPAA documentation, and compliance pages for healthcare SaaS platforms. Ensures Google Play/App Store approval and GDPR/HIPAA compliance.

lc-test

16
from diegosouzapw/awesome-omni-skill

Test a Rust solution file against LeetCode's test cases (project)

laravel-security-audit

16
from diegosouzapw/awesome-omni-skill

Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.

kube-audit-kit

16
from diegosouzapw/awesome-omni-skill

Performs read-only Kubernetes security audits by exporting resources, sanitizing metadata, grouping applications by topology, and generating PSS/NSA-compliant audit reports. Use when the user requests auditing Kubernetes clusters, Namespaces, security reviews, or configuration analysis.

jwt

16
from diegosouzapw/awesome-omni-skill

JWT y auth. Proyecto usa este skill; contenido canónico en .ai-system.

jwt-verify

16
from diegosouzapw/awesome-omni-skill

Implement JWT verification middleware in FastAPI for user auth. Use when securing APIs or handling tokens.

jules-audit-request

16
from diegosouzapw/awesome-omni-skill

Protocol for escalation to Jules when stuck.

istio

16
from diegosouzapw/awesome-omni-skill

Service mesh implementation with Istio for microservices traffic management, security, and observability. Use when implementing service mesh, mTLS, traffic routing, load balancing, circuit breakers, retries, timeouts, canary deployments, A/B testing, or service-to-service communication. Triggers: istio, service mesh, envoy, sidecar, virtualservice, destinationrule, gateway, mtls, peerauthentication, authorizationpolicy, serviceentry, traffic management, traffic splitting, canary, blue-green, circuit breaker, retry, timeout, load balancing, ingress, egress, observability, tracing, telemetry.