Loading...
Loading...
Found 149 Skills
Gold-standard code review for SAP CC Go repositories against the project's lead review standards. Dispatches 10 domain-specialist agents in parallel — each loads domain-specific references and scans ALL packages for violations in their assigned domain. Produces a prioritized report with REJECTED/CORRECT code examples. Optional --fix mode applies corrections on a worktree branch. This is the definitive "would this code pass lead review?" assessment.
Deterministic plan lifecycle management via scripts/plan-manager.py CLI. Use when user asks to list, show, create, check, complete, or abandon plans, or when session starts and stale plans need surfacing. Use for "check plans", "what's on our plan", "mark task done", "finish this plan", or "create a plan". Do NOT use for executing plan tasks, modifying plan content directly, or performance/refactoring work unrelated to plan tracking.
Perses plugin scaffolding and creation: select plugin type (Panel, Datasource, Query, Variable, Explore), generate with percli plugin generate, implement CUE schema and React component, test with percli plugin start, build archive with percli plugin build. Use for "create perses plugin", "new panel plugin", "new datasource plugin", "perses plugin scaffold". Do NOT use for dashboard creation (use perses-dashboard-create).
CUE schema authoring for Perses plugins: define data models, write validation constraints, create JSON examples, implement Grafana migration schemas in migrate/migrate.cue. Educational skill that explains CUE patterns specific to Perses plugin development. Use for "perses cue schema", "perses model", "plugin schema", "cue validation perses". Do NOT use for dashboard CUE definitions (use perses-dac-pipeline).
Validate plans against 10 verification dimensions before execution begins. Uses goal-backward analysis to catch dropped requirements, vague tasks, missing dependencies, and scope overreach. Produces PASS/BLOCK verdict with structured findings. Use for "check plan", "validate plan", "is this plan ready", "review plan before executing", or "/plan-checker". Do NOT use for plan creation (use feature-plan or workflow-orchestrator) or plan lifecycle management (use plan-manager).
Manually teach Claude Code an error pattern and its solution, storing it in the learning database with high confidence. Use when user provides an explicit "error -> solution" pair, wants to pre-load fix knowledge, or corrects a previous bad fix. Use for "/learn", "teach pattern", "remember this fix". Do NOT use for automatic error learning (that is the error-learner hook), debugging live issues, or querying existing patterns.
Run Go quality checks via make check with intelligent error categorization and actionable fix suggestions. Use when user requests "run quality checks", "check PR quality", "verify code quality", or "run make check". Use before creating commits or during PR review. Do NOT use for non-Go repositories, repositories without a Makefile, or manual linter invocation.
WordPress REST API integration for posts and media via deterministic Python scripts. Use when uploading articles, creating drafts, publishing posts, uploading images, editing existing posts, or managing WordPress content. Use for "upload to wordpress", "create wordpress draft", "publish to your-blog", "upload image", or "edit wordpress post". Do NOT use for writing articles (use blog-post-writer) or editing prose style (use anti-ai-editor).
Run Vitest tests and parse results into actionable output. Use WHEN user needs to run JavaScript/TypeScript tests in a Vitest-configured project, verify test suites pass, or get structured failure reports. Use for "run tests", "vitest", "check if tests pass", or "test results". Do NOT use for Jest/Mocha projects, installing dependencies, writing new tests, or auto-fixing failing assertions.
Spawn 10 independent parallel agents to analyze source material from distinct perspectives, synthesize findings, and apply improvements to a target agent or skill. Use when source material is complex and multi-angle extraction justifies 3-5x token cost over inline analysis. Use for "parallel analysis", "multi-perspective", or "deep extraction". Do NOT use for routine improvements, simple source material, or when token budget is limited.
Local branch cleanup after PR merge: identify, switch, delete, prune in 4 steps. Use when a PR has been merged and local branches need cleanup, when stale branches accumulate, or when user says "clean up branches", "delete merged branch", or "prune". Do NOT use for branch creation, PR review, or CI checks.
Mobile development patterns for React Native and Flutter including navigation, state management, and responsive design