Awesome-omni-skill done

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

install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/testing-security/done" ~/.claude/skills/diegosouzapw-awesome-omni-skill-done && rm -rf "$T"
manifest: skills/testing-security/done/SKILL.md
source content

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.