validate-and-regenerate-parameters
Validates parameters.py, checks for errors, and regenerates _variables.yml. Use when editing parameters, adding new values, or ensuring variable consistency.
Essential command-line tools and system utilities.
Validates parameters.py, checks for errors, and regenerates _variables.yml. Use when editing parameters, adding new values, or ensuring variable consistency.
Identifies and helps refactor Elixir anti-patterns including code smells, design issues, and bad practices
出力ディレクトリ初期化 - リファクタリング分析用の出力ディレクトリ構造を作成。/init-output [出力パス] で呼び出し。
Generate the next sequential file or folder name for directories with numbered prefixes (e.g., 01-setup.md, 02-init.md). Use when creating a new file or folder that should follow an existing numbering sequence, when adding to a sequentially-named series, or when the user asks for the "next" numbered item in a directory.
Autonomously audit the entire repository and update the main README with comprehensive, accurate documentation of the current codebase
Fast codebase search via WarpGrep (20x faster than grep)
Generate a changeset file for the current changes following the changesets pattern used in the project.
Manage specification files for spec-driven development. Use when creating, updating, or deleting spec files. Supports feat, fix, docs, refactor, and chore scopes.
Cleans and maintains Package.swift files in a Clean Architecture–oriented Swift project. Use when removing obsolete dependencies, refactoring module graphs, or enforcing architectural conventions encoded in Package.swift.
Fast code search using ripgrep (rg) with smart defaults, regex patterns, and file filtering. Use when searching for text patterns, code snippets, or performing multi-file code analysis.
Generate structured changelogs for app releases from git history. Use when preparing releases, documenting changes, or creating version notes.
Write safe context expressions in Claude Code slash command files. Covers backtick expressions, find vs ls patterns, and commands that always exit 0. Use when creating slash commands, writing context sections with backtick expressions, or debugging command execution failures.
Command-line tool development patterns and conventions. Use when: - Building CLI applications - Designing command interfaces - Implementing help and error messages - Choosing CLI frameworks - Following Unix conventions Keywords: CLI, command line, terminal, help text, exit codes, flags, arguments, Commander, Thor, Cobra
Use when you need to test Nix expressions, validate Nix configuration syntax before applying, debug Nix code or understand evaluation results, inspect derivation attributes, or evaluate flake outputs and inputs
Creates and configures Claude Code slash commands with YAML frontmatter, argument handling, and tool permissions. Use when building new commands, adding $ARGUMENTS or $1-$N parameters, configuring allowed-tools, organizing command namespaces, or fixing command failures.
Comprehensive code review for Golang CLI applications. Produces an actionable checklist covering error handling, CLI framework patterns (Cobra/urfave), testing, performance, security, and Go idioms. TRIGGERS: Review Go CLI, review golang command-line, code review .go CLI, audit CLI application, check golang tool, review cobra app
Use when switching ALTO orchestrator modes (dev/build/setup). Guides mode transitions and session management via the alto command.
Initialize .claude/ structure and surgically add PopKit section to CLAUDE.md without overwriting. Detects conflicts, creates config, prompts for Power Mode. Use for new projects only - use analyze-project for existing.