Loading...
Loading...
Found 149 Skills
Systematic 4-phase codebase exploration: Detect, Explore, Map, Summarize. Use when starting work on an unfamiliar codebase, onboarding to a new project, reviewing a repository for the first time, or building context before debugging or code review. Use for "explore codebase", "what does this project do", "understand architecture", or "onboard me". Do NOT use for modifying files, running applications, performance optimization, or deep domain analysis.
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.
Audit and maintain blog taxonomy (categories/tags) for consistency, SEO, and navigation: scan content, detect orphans and duplicates, merge and rename terms, verify builds. Use when user asks to "audit tags", "fix taxonomy", "consolidate categories", "merge tags", or "clean up taxonomy". Do NOT use for writing new content, individual post SEO optimization, or major content restructuring.
Deterministic audit of cron/scheduled job scripts for reliability, error handling, logging, cleanup, and concurrency safety. Use when user says "audit cron", "check cron script", "cron best practices", "scheduled job review", or "bash script audit". Do NOT use for crontab scheduling syntax, systemd timers, or general shell linting without a cron/scheduled-job context.
Voice-integrated blog post creation with 4-phase workflow: Assess, Decide, Draft, Preview. Use when user wants to write a blog post, create content for a Hugo site, or draft an article using a specific voice profile. Use for "write post", "blog about", "draft article", "create content", or "write about [topic]". Do NOT use for editing existing posts, voice profile creation, SEO optimization, or social media content.
Collaborative design phase for feature lifecycle: explore requirements, discuss trade-offs, produce design document. Use when starting a new feature that needs design before implementation. Use for "design feature", "let's think through", "explore approaches", or "/feature-design". Do NOT use for simple bug fixes or tasks that don't need design discussion.
Read public Bluesky feeds via the AT Protocol API. Fetch recent posts from any public profile or search a profile's posts by keyword. No authentication required. Use for "read bluesky", "check bluesky feed", "search bluesky posts".
Merge validated feature to main via PR, tag release, cleanup worktree. Use after /feature-validate passes. Use for "release feature", "merge feature", "ship it", or "/feature-release". Do NOT use without passing validation or for hotfixes that skip the pipeline.
Multi-language code quality gate with auto-detection and language-specific linters. Use when user asks to "run quality checks", "quality gate", "lint all", "check everything", "pre-commit checks", or "is this code ready to commit". Use for verifying code quality across polyglot repos. Do NOT use for single-language linting (use code-linting) or comprehensive code review (use systematic-code-review).
Capture a writer's voice DNA through collaborative interview and sample analysis. Use when someone wants to document their writing voice for use with a ghost writer skill. Produces a Voice DNA Document with patterns, anti-patterns, and actionable guidance. Handles one register/mode per session, supports refinement over time.
Idiomatic Go patterns for error handling, interfaces, concurrency, testing, and module management
Data engineering patterns for ETL pipelines, data warehousing, Apache Spark, and data quality validation