Help us improve
Share bugs, ideas, or general feedback.
From hephaestus
Use when implementation is complete and all tests pass — guides branch completion by presenting structured options for merge, PR creation, or cleanup
npx claudepluginhub homericintelligence/projecthephaestus --plugin hephaestusHow this skill is triggered — by the user, by Claude, or both
Slash command
/hephaestus:finish-branch <optional: base branch name><optional: base branch name>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide completion of development work by verifying work is done, then presenting clear options.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Guide completion of development work by verifying work is done, then presenting clear options.
Core principle: Verify tests → Run verification → Present options → Execute choice → Clean up.
Prerequisite: Run /hephaestus:verification BEFORE invoking this skill. If verification fails, fix the issues first.
Run the complete Hephaestus verification suite:
pixi run pytest tests/unit -v
pixi run mypy hephaestus/
pixi run ruff check hephaestus/ tests/
pixi run ruff format --check hephaestus/ tests/
pre-commit run --files $(git diff --name-only origin/main)
If ANY check fails:
Verification failing — must fix before completing:
[Show failures]
Cannot proceed with merge/PR until all checks pass.
Stop. Don't proceed to Step 2.
If all checks pass: Continue.
The main branch is protected in all HomericIntelligence repos. All merges go through PRs.
git log --oneline origin/main..HEAD
Verify the commit list looks correct before proceeding.
Present exactly these options:
All checks pass. What would you like to do?
1. Push and create a Pull Request (recommended — main is protected)
2. Keep the branch as-is (I'll handle it later)
3. Discard this work
Which option?
Note: Direct merge to main is not an option — the main branch is protected.
# Push branch
git push -u origin <feature-branch>
# Create PR. Per repo policy: body MUST contain a literal "Closes #N" line,
# every commit MUST be signed, and auto-merge MUST be enabled. The CI gate
# pr-policy blocks any PR that violates one of these.
gh pr create \
--title "feat(scope): description" \
--body "$(cat <<'EOF'
## Summary
- <bullet: what changed>
- <bullet: why>
## Test Plan
- [ ] All unit tests pass
- [ ] Type check passes
- [ ] Linter clean
- [ ] Pre-commit hooks pass
Closes #<issue-number>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"
# Enable auto-merge (mandatory under repo PR policy).
# Pick the method this repo actually allows (rebase -> squash -> merge).
HELPER=""
for cand in \
"${HEPHAESTUS_REPO_ROOT:-}/scripts/choose_merge_flag.sh" \
"$(git rev-parse --show-toplevel 2>/dev/null)/scripts/choose_merge_flag.sh" \
"$HOME/Projects/ProjectHephaestus/scripts/choose_merge_flag.sh"; do
if [ -r "$cand" ]; then HELPER="$cand"; break; fi
done
if [ -n "$HELPER" ]; then
. "$HELPER"
MERGE_FLAG=$(choose_merge_flag "$(gh repo view --json nameWithOwner --jq .nameWithOwner)") \
|| MERGE_FLAG="--squash" # safe org-wide default per HomericIntelligence policy
else
MERGE_FLAG="--squash"
fi
gh pr merge --auto "$MERGE_FLAG"
Then: Cleanup worktree (Step 5)
Report: "Keeping branch <name>. Worktree preserved at <path>."
Don't cleanup worktree.
Confirm first:
This will permanently delete:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path> (if applicable)
Type 'discard' to confirm.
Wait for exact typed confirmation.
git checkout main
git branch -D <feature-branch>
Then: Cleanup worktree (Step 5)
# Check if in a worktree
git worktree list
# If yes, remove it
git worktree remove <worktree-path>
git worktree prune
All commits must follow conventional commits:
feat(scope): add new capability
fix(scope): resolve specific issue
docs(scope): update documentation
refactor(scope): restructure without behavior change
test(scope): add/fix tests
chore(scope): maintenance task
Include Co-Authored-By trailer when AI-assisted:
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Never:
Always:
Adapted from obra/superpowers under the MIT License. Copyright (c) 2025 Jesse Vincent.