claude

tidy

Careful low-risk codebase cleanup across 7 focused tracks: deduplication, type consolidation, dead code removal, circular dependency untangling, type strengthening, error-handling cleanup, and deprecated/AI-slop removal. Each track inspects in parallel (read-only), writes a critical assessment, ranks proposed changes by confidence (HIGH / MEDIUM / LOW / UNCERTAIN), and auto-applies ONLY HIGH-confidence LOW-risk changes per batch — running language-appropriate type checks, tests, and lints after each. MEDIUM and LOW changes get surfaced for explicit human decision. Atomic git commits per batch so any failing check is one revert away. Anti-pattern guardrails: never merges code that just LOOKS similar; never removes dynamically-imported / config-referenced / framework-convention / generated code; never strips legitimate boundary types (JSON parses, external APIs, FFI); never silences real error boundaries; never introduces new abstractions just to break a cycle; never uses comments as the source of truth. Refuses to run on a dirty working tree. Default mode is --dry-run (assess only); --apply is opt-in with a checkpoint before changes; --auto skips the checkpoint but never the HIGH-only confidence gate.

3 on GitHubby AlphaBravov0.1.0MITupdated 3 months agoproductivity
/

Plugin tidy from marketplace codsworth in AlphaBravoCompany/codsworth-marketplace. Commands read from the repo's manifest — 1 month ago.

What it installs

Slash commands (4)

  • /tidy:apply

    Apply HIGH-confidence changes from a previous tidy dry-run

  • /tidy:help

    Explain the tidy plugin

  • /tidy:run

    Run a careful low-risk cleanup pass across 7 focused tracks

  • /tidy:status

    Show recent tidy runs and their status

Subagents (8)

  • circular-deps

    Tidy Track 4 — Circular dependency untangling. Maps the full dependency graph using language-appropriate tools (madge for JS/TS, gomodgraph + custom Go AST scan for Go), identifies every cycle, and prioritizes those that affect maintainability, testability, or correctness. Untangles by extracting sh

  • dead-code

    Tidy Track 3 — Dead code removal. Uses language-appropriate static analysis (knip, ts-prune, depcheck for JS/TS; deadcode, unused, golangci-lint for Go; vulture for Python) to find unused exports, unreferenced functions, and orphaned files. Then MANUALLY verifies each candidate against dynamic impor

  • dedup

    Tidy Track 1 — Deduplication. Scans the entire codebase for repeated logic, copy-pasted functions, and redundant abstractions. Proposes consolidation ONLY where it genuinely reduces complexity without obscuring intent. Forbidden from merging code that merely LOOKS similar but serves different purpos

  • deprecated-slop

    Tidy Track 7 — Deprecated code + AI slop. Finds legacy, deprecated, and fallback code paths; removes only what is CLEARLY obsolete and not required for compatibility or active users. Also finds AI artifacts (stubs, placeholder logic, edit-history comments, narration of changes instead of explanation

  • error-cleanup

    Tidy Track 6 — Error-handling cleanup. Finds every try/catch and equivalent defense pattern; removes the ones silently swallowing errors, hiding failures, or falling back to defaults that mask real problems. Keeps error handling that serves a real boundary, real recovery, real logging, real cleanup,

  • reviewer

    Tidy reviewer. Reads all 7 tracks' applied changes after the apply phase, runs the full check matrix one more time, and produces a consolidated debrief. Catches conflicts between tracks (e.g., dedup merged a function that dead-code was about to remove). Reads only applied changes and the final state

  • type-consolidate

    Tidy Track 2 — Type consolidation. Finds type definitions scattered across files, identifies duplicates that have quietly drifted out of sync, merges them into a single source of truth. Distinguishes legitimately-distinct types (same name, different purpose) from accidentally-duplicated types (same

  • type-strengthen

    Tidy Track 5 — Type strengthening. Finds every instance of `any`, `unknown`, `interface{}`, weak generics, and other weak-type placeholders that AI left behind. Researches what the real types should be by inspecting the codebase, related packages, and actual runtime usage. Replaces with strong types

View source on GitHub

More from AlphaBravoCompany/codsworth-marketplace

All 11 plugins →

foundry

claude

Autonomous build-verify-fix loop. Decomposes a spec into castings with pre-authored teammate prompts, validates them through an 11-dimension F0.9 gate (including F0.7 intent-carrier coverage), builds in parallel waves with server-side evidence re-execution and per-requirement-ID binding, runs up to 8 verification streams (TRACE, FLOW_TRACE, PROVE, RESEARCH_AUDIT, COVERAGE_DIFF, SIGHT, TEST/PROBE, TEST_OBSERVATIONS), grinds defects to zero, then assays the result with fresh-eyes verification. Brownfield runs consume a flow delta; greenfield and cosmetic runs use the end-state pipeline. Forge plans. Foundry builds.

4 skills · 6 commands · 15 agents

3

adhoc

claude

Stops Claude from racing on ad-hoc work. Methodical-mode pre-response checklist injected every turn (Restate, Verified/Unverified assumptions, Read Floor, Approach Deliberation, Blast Radius, Stall Check, Competing Hypotheses, Goal-Driven Execution). Stop hook enforces four gates: file:line citation verifier, uncertainty-tell scanner, zero-tool-call grounding audit, and an iterative two-tier critic-dialog (Haiku fast-critic rounds 1-2, opus pre-stop-critic rounds 3-5, HARD block at round 5 until /adhoc:trust-me bypass). Each critic runs a 10-item rule compliance audit and sees the prior round's feedback to verify Claude actually addressed flagged issues. /adhoc:casual (one turn skip), /adhoc:trust-me (one-turn strict bypass), /adhoc:off (session disable). /adhoc:deep for heavier analysis, /adhoc:second-opinion for independent critique.

1 skill · 12 commands · 3 agents · hooks

3

crew

claude

Throw an AI dev at a problem and have it own the outcome. Five Opus agents (router, scout, worker, critic, fresh-eyes) collaborate to investigate, plan, execute, and verify — SSH into systems, spin up infra, edit code, ship features, debug deploys, get airgap bundles working. Worker self-switches between investigating, planning, executing, and verifying modes — one persistent persona, not five different ones. Bounded scout budget (25 tool calls / 5 min, doubled in --paranoid), multi-agent reflexion on stuck (N=2-3 parallel variants + judge — fixes Reflexion's degeneration-of-thought failure mode), critic and fresh-eyes both produce mandatory evidence ledgers of commands they actually ran. One checkpoint (plan approval) for side-effecting tasks, zero for pure investigation. Plan and debrief render in chat; state files exist in .crew/runs/ for resume. Production beats --yolo always. /crew:goal sets a completion condition and runs the worker→critic→fresh-eyes loop unattended — cycle after cycle until critic and fresh-eyes both return pass, or a cycle/time cap stops it — enforced by a Stop hook (goal-gate.py) that blocks the run from ending while the goal is unmet.

6 commands · 5 agents · hooks

3

e2e

claude

End-to-end test authoring and maintenance for web apps via Playwright + Playwright MCP. Claude drives a real browser, reads the accessibility tree, and emits *.spec.ts files that pass — then keeps them passing. /e2e:init scaffolds Playwright in the cwd and registers the MCP server. /e2e:write <flow> drives the browser to perform the flow and emits a green spec. /e2e:crawl discovers every route and generates a smoke spec per route. /e2e:matrix produces a routes × roles coverage suite with reused storageState. /e2e:audit runs the suite, reads trace.zip files, and triages failures by root cause. /e2e:record wraps playwright codegen for manual capture. The author skill enforces selector hygiene (getByRole over CSS), auto-wait discipline, and idempotent test design; the diagnose skill drives trace-driven flaky-test triage. The spec-writer subagent isolates MCP-driven spec authoring from the main context.

2 skills · 7 commands · 1 agent

3

forge

claude

Codebase-aware specification engine. Runs a grounded interview that captures implicit facts as A-AUTO-NNN entries, emits typed Global Invariants / State Transitions / Contracts tables, runs an adversarial spec review at R3.5, and writes a foundry-ready spec with version frontmatter — locked, classified, and verifiable. Brownfield runs produce a flow delta against the existing system; greenfield runs produce an end-state spec; cosmetic runs skip flow mapping. Forge plans. Foundry builds.

4 commands · 3 agents

3

crucible

claude

A mini-foundry — the build-verify-fix engine without the MCP server or the planning interview. You bring a structured spec (markdown with stable requirement IDs + acceptance criteria); crucible builds it and refuses to let it drift. /crucible:build <spec-file> decomposes the spec into units with DISJOINT file ownership, shows the split for one approval, then runs a Workflow engine: CAST (parallel deliberate-engineering builders, each handed its unit prompt verbatim, each emitting re-executable evidence bound to requirement IDs) → INSPECT (three blind orthogonal streams — wiring exists/substantive/wired, spec-before-code fresh-eyes assay, and re-execution of every evidence command) → GRIND (every non-passing verdict is a defect; fix the affected units and full-re-inspect, loop until zero or a cycle cap) → ASSAY (fresh-eyes agents read the spec first, form expectations, then confirm each requirement). Refuses a dirty tree; edits the shared working tree under disjoint ownership; commits per-unit only on user say-so so any unit is one revert away. Keeps foundry's load-bearing principles — verbatim unit prompts (no interpretation layer), multi-stream blind verification (build-green ≠ done), evidence binding, defect-to-zero grind, spec-before-code assay, an engine that routes and verifies but never re-narrates the spec or judges the code itself. Drops what needs the heavy machinery: no MCP gates/hashing, no isolated-worktree evidence, no brownfield flow-graph interview. forge plans → foundry builds; crucible is foundry's build engine, mini.

2 commands · 2 agents

3

Similar plugins

caveman

claude

Talk like caveman. Cut filler. Keep technical details explicit.

22 skills · 1 command · 3 agents · hooks

JuliusBrussee/caveman 119,462

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

pake

claudecodex

Package any website or local web build into a lightweight desktop app with Pake CLI.

1 skill

tw93/Pake 63,463

Maintain tidy?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins11 plugins