xander-local

Plugin xander-local from marketplace xander-plugins in Xander-git/xander-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (6)

• dedupe-scanner

  Audit a codebase for extractable duplication and propose targeted refactors. Use this whenever the user asks for a code review focused on duplication, DRY violations, repetition, magic values, code smells, cleanup, or extraction opportunities. Also use proactively when the user shares multiple modul

• execute-plan-orchestration

  Use when planning subagent execution of a multi-task implementation plan — deciding how many subagents to dispatch, how to group tasks, which model each gets, and where review gates go. Turns a task list + dependency DAG into clusters sized for one agent each. Trigger after writing-plans, before dis

• plan-refinery

  Use when a design spec and implementation plan are drafted and should be iterated to convergence before execution — dispatches a reviewer panel (general, data-flow, simplicity, plus specialists) in a loop, merges severity-tagged concerns into a provenance-locked ledger, applies plan fixes, gates all

• porting-a-reference-algorithm

  A checkable procedure for transcribing an external algorithm (a paper, or a reference implementation) into a codebase. Use whenever matching code to an outside source — before making any claim about what that source does. Covers assembling references, citing file:line, diffing not inspecting, pinnin

• present-solutions

  Present multiple candidate solutions to a problem or open question, each with background, tradeoffs (accuracy, implementation cost, complexity, technical debt, plus domain-specific axes), failure modes, and a reasoned recommendation. Use this skill whenever the user is weighing design choices, compa

• summarize-session

  Generate a shareable, evidence-gated write-up of the CURRENT Claude Code session — what was asked, how it was steered, what was built, and what was learned. INVOKE ONLY ON EXPLICIT REQUEST — never proactively or automatically. Trigger only when the user explicitly asks for it, e.g. "summarize this s

Subagents (5)

• data-flow-reviewer

  Fixed panel member of the plan-refinery loop. Traces every user-facing flow in a design spec end-to-end — entry point, validation, state, computation, persistence/output, result surfaced back — and hunts broken chains, boundary contract mismatches, orphaned inputs/outputs, and stale-state hazards. D

• general-reviewer

  Fixed panel member of the plan-refinery loop. Reviews a design spec + implementation plan for spec↔plan traceability (coverage gaps, scope creep, contradictions), feasibility against the real codebase, and failure modes (edge cases, partial failures, idempotency). Dispatch via the plan-refinery skil

• implementation-test-reviewer

  Use when a logical chunk of functionality is complete and you need a review that validates implementation correctness AND whether its tests genuinely prove that correctness. Hunts bugs and edge cases, then checks the test suite for false greens — tests that pass without exercising the code paths the

• plan-reviewer

  Use when an implementation plan has been drafted and needs critical review for feasibility, correctness, and optimality before implementation begins. Validates logic against the real codebase, verifies external API claims, hunts race conditions, and challenges unnecessary complexity. Spawn after a p

• simplicity-reviewer

  Fixed panel member of the plan-refinery loop — the counterweight that prunes instead of adds. Reads ONLY the spec, plan, context brief, and ledger (no codebase traversal) and asks what can be removed while still satisfying the spec. May challenge the spec itself against its Objective & Non-goals; al

Similar plugins