Orchestrate full development workflow. Use when implementing features, starting structured development, or user mentions "workflow" or "implement issues".
/plugin marketplace add beshkenadze/claude-skills-marketplace/plugin install beshkenadze-skills-marketplace@beshkenadze/claude-skills-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
CODE-REVIEW.mdERRORS.mdPARALLEL.mdTESTING.mdOrchestrates complete feature development from issue to merge: Issue → Branch → Worktree → Implement → Test → Review → PR → Merge → Close.
mcp__gitea__*, GitHub: mcp__github__*)codex --version)Gitea MCP:
mcp__gitea__get_issue_by_index(owner, repo, index)
GitHub MCP:
mcp__MCP_DOCKER__get_issue(owner, repo, issue_number)
GitHub CLI:
gh issue view {issue_number} --repo {owner}/{repo}
git checkout main && git pull origin main
git checkout -b feature/{issue-number}-{slug}
git worktree add ../worktrees/feature-{issue}-{slug} feature/{issue}-{slug}
Copy vendor dependencies if present:
cp -R Vendor ../worktrees/feature-{slug}/
Work in worktree. For complex tasks, use Task tool with sub-agents.
Add tests for new functionality. See TESTING.md for testing patterns.
Project-specific test command (e.g., xcodebuild test, npm test).
Ask user which tool to use if not specified:
codex review --base maingemini -p "/code-review"gh copilot (interactive, ask for review)opencode -p "review changes" (provider-agnostic)Run exactly once per review cycle:
# Codex (detailed P1-P4 findings)
codex review --base main
# OR Gemini (quick quality analysis)
gemini -p "/code-review"
# OR GitHub Copilot (interactive)
gh copilot # then ask: "review my changes against main"
# OR OpenCode (works with any LLM provider)
opencode -p "review my code changes against main branch"
IMPORTANT: Wait for the full output. Do NOT run a second review unless you've made code changes to fix issues.
If critical/high issues found:
If no critical issues: Proceed to commit.
See CODE-REVIEW.md for handling specific findings.
git add . && git commit -m "feat(scope): description"
git push -u origin feature/{issue}-{slug}
Gitea MCP:
mcp__gitea__create_pull_request(owner, repo, title, body, head, base="main")
GitHub MCP:
mcp__MCP_DOCKER__create_pull_request(owner, repo, title, body, head, base)
GitHub CLI:
gh pr create --title "title" --body "body" --base main --head feature/{issue}-{slug}
git checkout main && git pull origin main
git merge feature/{issue}-{slug} --no-ff && git push origin main
Gitea MCP:
mcp__gitea__edit_issue(owner, repo, index, state="closed")
GitHub MCP:
mcp__MCP_DOCKER__update_issue(owner, repo, issue_number, state="closed")
GitHub CLI:
gh issue close {issue_number} --repo {owner}/{repo}
git worktree remove ../worktrees/feature-{issue}-{slug}
git branch -d feature/{issue}-{slug}
For multiple independent issues, see PARALLEL.md.
See ERRORS.md for handling build failures, Codex P1 issues, and merge conflicts.
Input: "Implement issue #42 - Add user authentication"
Process:
feature/42-user-authOutput:
✅ Issue #42 implemented
✅ PR #15 created and merged
✅ Issue #42 closed
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.