Command Claude Code
Source: https://github.com/anthropics/claude-plugins-official Pinned commit: 6bfd4e0c6d3da6050984fa5ed8281d915fa7ed69 (2026-09-23) Upstream path: plugins/commit-commands/commands/commit.md License: Apache-2.0 -- complete terms in .claude/skills/claude-md-improver/LICENSE.txt (byte-identical to this plugin's LICENSE)…
Command Claude Code
Update CLAUDE.md with learnings from this session.
Skill Claude Code
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Skill Claude Code needs its repo
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
Skill Claude Code
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Skill Claude Code
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available.
Skill Claude Code
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
Skill Claude Code
Makes a vague request buildable (9 ingredients, F1-F13, one 2-3-option question): vague/one-word asks, "maak het beter", a bug without symptom, before intake, or to help users ask better.
Skill Claude Code
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
Skill Claude Code
A relentless interview to sharpen a plan or design.
Skill Claude Code
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Skill Claude Code
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude Code
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Skill Claude Code
Use when you need to resolve an in-progress git merge/rebase conflict.
Skill Claude Code
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Skill Claude Code needs its repo
Use when executing implementation plans with independent tasks in the current session.
Skill Claude Code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Claude Code
Teach the user a new skill or concept, within this workspace.
Skill Claude Code
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude Code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
Skill Claude Code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude Code
Stop. That last message did not land: re-pitch it.
Skill Claude Code
Use when you have a spec or requirements for a multi-step task, before touching code.
Skill Claude Code needs its repo
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
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: