A command is the one you type. It runs exactly when you ask it to, and never before.
4,574 commands across 357 plugins.
Gather implementation context before starting a task. Delegates to context-gatherer subagent (Sonnet) to pre-fetch everything Opus needs.
Delegate test execution to the test-runner subagent (Sonnet) and apply approved fixes in the main session
Incident response workflow — triage, evidence collection, timeline, and IOC extraction
Post-exploitation workflow after getting shell access — privesc, credential harvest, lateral movement
Generate a professional penetration test report from all evidence files
Spawn a teammate to work on a separate task independently. You continue your own work and get notified when the teammate finishes.
A structured way to plan complex features before implementing. Works through: Problem → Options → Solution → Stories → Finalize.
Trigger a code review on your recent changes using the comprehensive-review plugin. This is Step 3 in the Development Flow — review before committing.
Review branch changes against Archcore docs, or report project health; --drift runs staleness detection, --deep a full documentation audit.
Run a lightweight Socratic design dialogue (3-5 AUQ rounds) and write a spec markdown file before any implementation work. Use BEFORE /plan feature when…
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog…
Generate Divi 5-ready CSS for a component, section, or page element. Outputs in the format you specify (Theme Options, Code Module, Child Theme, or Free-Form…
Research the latest Divi 5 updates, features, CSS compatibility changes, and best practices. Updates plugin knowledge base with new findings.
Check that a Divi 5 page works across device sizes (small phones, iPhones, tablets, laptops, widescreen, ultrawide). Uses live viewport testing via a browser…
Use when: querying past work, managing memories, or checking project history
Use when: user asks to remember something, after solving a non-obvious problem, or to capture key session findings
Use when: importing skills/agents from GitHub, managing registry resources, or searching for tools to solve a problem
Show the stored final output for a finished Gemini job in this repository
Check whether the local Gemini CLI is ready and optionally toggle the stop-time review gate
Read and update working memory — maintain context across sessions via CONTINUITY.md
Systematic debugging — 4-phase root cause process with defense-in-depth verification
Interactive onboarding tour — discover CodyMaster skills, workflows, and examples. Run this first to learn how to use the kit.
Query the Android/AOSP kernel CVE database by CVE id, version, build date, or branch
Deep scan of Windows Registry for malware persistence and unauthorized modifications
Scan file system for suspicious files in common malware locations
Check OCR installation and verify all dependencies are available.
Generate a Code Review Map to help navigate large, complex changesets.
`/prd` Phase 3에서 선택한 API 유형의 상세 템플릿. REST / GraphQL / gRPC / WebSocket / OpenAPI 템플릿과 로그인 API 예시를 담고 있다. 필요한 유형 섹션만 참고하여 PRD §5.1 API Specification을 작성한다.
GitHub PR을 터미널에서 리뷰합니다. PR diff를 분석하고, 코드 리뷰 점수를 매기고, 리뷰 코멘트를 남깁니다. Trigger on "/review-pr", "PR 리뷰해줘", "리뷰해줘", "PR 봐줘", "코드 리뷰", "review this PR".
Generate screen specifications (IA / User Flow / Screen Spec / Wireframe / Dev Handoff) from an existing PRD. Trigger keywords: - Commands: "/screen-spec",…
Full CVE hunting pipeline. Usage: /hunt <package-name>. Orchestrates all agents: registry check, clone, code review, PoC build, validation, and report…
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic