Agent Claude Code
Runs type checking, linting, and builds after code changes. Use proactively after edits.
Agent Claude Code
Runs type checking, linting, and builds after code changes. Use proactively after edits.
Agent Claude Code
Root cause analysis for bugs and unexpected behaviour. Use when debugging issues.
Agent Claude Code
Validates proposed changes follow existing codebase patterns. Use proactively before implementing features or refactoring code.
Agent Claude Code
Reviews planned changes for scope creep. Use before starting implementation of features or refactoring.
Skill Claude Code
Work through a PR's unresolved review comments one at a time. Detects the repo's stack, fetches the unresolved threads, reproduces each reviewer's claim before touching anything, fixes only what the probe confirmed, proves the fix with the same probe, presents it, then commits that one thread before moving on.
Skill Claude CodeCodex
Generate git commit messages, splitting work into granular commits by concern. Use when user says "commit this", "write a commit", "commit message", or invokes /commit.
Skill Claude CodeCodex
Write PostgreSQL trigger functions and migrations for this Supabase project. Enforces all security and performance rules derived from the project's migration history to avoid Supabase advisor warnings (lints 0011, 0028, 0029).
Skill Claude CodeCodex
This skill should be used when the user asks "how does this work", "what patterns are used here", "show me how this is done in the codebase", or before implementing features to understand existing conventions. Explores codebase patterns for types, components, validation, data fetching, and file organization without…
Skill Claude CodeCodex
This skill should be used when the user reports a bug, asks to "fix this bug", "debug this issue", "something is broken", "this isn't working", or requests investigation of unexpected behavior. Enforces minimal scope changes, prevents touching working code, and includes build verification steps.
Skill Claude CodeCodex
Explore codebase and update CLAUDE.md with detected frameworks, patterns, and conventions.
Skill Claude CodeCodex
Explore codebase and update project-context.md with detected frameworks, patterns, git context, and current focus.
Skill Claude Code
Thorough, structured code review of the current branch's PR (or of the branch diff when no PR exists). Derives PR, base branch, stack and conventions from the repo, resolves the ticket for acceptance criteria, and probes every finding before reporting it.
Skill Claude Code
This skill should be used when the user asks to "refactor this code", "clean up this component", "reorganize these files", "consolidate duplicated code", "extract shared logic", or requests code restructuring. Forces a PLAN → APPROVE → EXECUTE workflow with phased changes and build verification between phases.
Skill Claude CodeCodex
Zod 4 syntax reference and migration guide. Use when writing Zod schemas to ensure correct Zod 4 patterns are used instead of deprecated Zod 3 syntax.
Agent Claude Code
Reviews code for over-engineering and unnecessary complexity. Use after writing code.
Command Claude Code
Find bug tickets assigned to me in a tracker (GitHub / Jira / Monday), fan out one worktree + Sonnet agent per ticket to fix them, open a draft PR each, and comment on the ticket only where the fix deviated from the spec.
Command Claude Code
Post code-review findings onto the open PR as a PENDING review - inline comments and suggestions in my own commenting voice - and write the summary to pr- -review.md in the repo root.
Command Claude Code
After a submitted PR review, pull maxitect's ACTUAL review comments from GitHub (not the draft from this context), the dev's replies, and the updated code - then report per-comment whether each item was implemented as suggested, implemented differently, declined with a reason, or ignored.
Command Claude Code
Prepare a concise PR and open it on GitHub against a base branch.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: