SuperJoe

Plugin superjoe from marketplace codingjoe in codingjoe/claude-plugins. Commands read from the repo's manifest — yesterday.

Skills (3)

• joe-audit

  Whole-repo audit for over-engineering. Scans the entire codebase, not a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", or "joe-au

• superjoe-code

  Write minimal code and review it. End after killJoe and stop for human review. Use superjoe-ship for tests and docs.

• superjoe-ship

  Add tests and docs to reviewed code. Run after superjoe-code and human review. Stop when coverage and docs pass.

Subagents (8)

• builderJoe

  Implement features, fix bugs, and refactor code. Use for code changes, feature implementation, and bug fixes. Do NOT use for writing tests, documentation, code review, security analysis, or multi-file orchestration.

• docuJoe

  Write and update documentation, docstrings, README files, and comments in superjoe-ship after tests pass. Use for documenting code, auditing docstrings, writing user-facing docs, or explaining design decisions. Do NOT use for code changes, reviews, or security analysis.

• inspectorJoe

  Review code for bugs, performance problems, naming violations, and test coverage gaps. Use for PR review, code audit, or checking for edge cases. Do NOT use for fixing issues found, docs, implementing features, or security audits.

• killJoe

  Cleanup tool for builderJoe's changes. Remove newly added tests, docstrings, and code comments. Run at the end of superjoe-code and after a cut in superjoe-ship.

• lazyJoe

  Guard against unnecessary code. Find over-engineering, bloat, and work another joe already owns, then delegate back. Do NOT write, fix, or document code yourself.

• researchJoe

  Research online documentation and find and evaluate packages on package indexes. Use to verify, compare, and vet dependencies and to read current docs. Do NOT use for code changes or test changes.

• secretJoe

  Find security vulnerabilities, evaluate exploitability, and provide proof-of-concept reproduction. Use for security audits, penetration testing, or vulnerability research. Do NOT use for fixing vulnerabilities found, writing documentation, making code changes, or general code review.

• testJoe

  Write tests for the reviewed code and run the test suite in superjoe-ship after human review. Do NOT use for writing production code, cutting branches, or docs.

Similar plugins