Loading...
Loading...
Found 141 Skills
Phase-gated git commit workflow with validation, staging, and CLAUDE.md compliance enforcement. Use when creating commits, staging changes, or when PR workflows need standardized commits. Triggers: "commit changes", "save work", "create commit", or internal skill invocation from PR workflows. Do NOT use for merge commits, rebases, amends, cherry-picks, or emergency rollbacks requiring raw git speed.
Fish shell configuration: config.fish, functions, abbreviations, variable scoping, conf.d modules, and PATH management. Use when user's $SHELL is fish, editing .fish files, working in ~/.config/fish/, or migrating from Bash. Use for "fish config", "fish function", "abbr", "conf.d", "fish_add_path", or "funcsave". Do NOT use for Bash/Zsh-only scripts, POSIX shell portability, or non-shell configuration tasks.
Deploy Perses server: Docker Compose for local dev, Helm chart for K8s, or binary for bare metal. Configure database (file/SQL), auth (native/OIDC/OAuth), plugins, provisioning folders, and frontend settings. Use when user wants to deploy, install, set up, or configure a Perses server instance. Use for "deploy perses", "install perses", "perses setup", "perses server", "run perses". Do NOT use for dashboard creation (use perses-dashboard-create) or plugin development (use perses-plugin-create).
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.
Safe bulk editing across multiple Hugo markdown posts: find/replace, frontmatter updates, content transforms with mandatory preview before apply. Use when user needs batch text replacement, bulk frontmatter field changes, heading/link/whitespace normalization, or regex-based content transforms across posts. Use for "batch edit", "find and replace across files", "add field to all posts", "bulk update tags". Do NOT use for single-file edits, structural refactoring, or content generation.
Coordinate PR mining to extract tribal knowledge and coding standards from GitHub PR history. Use when mining review comments, extracting coding rules, tracking mining jobs, or analyzing reviewer patterns across repositories. Use for "mine PRs", "extract standards", "coding rules from reviews", or "reviewer patterns". Do NOT use for code review, linting, static analysis, or writing new coding standards from scratch without PR data.
Validate Perses resources: run percli lint locally or with --online against a server. Check dashboard definitions, datasource configs, variable schemas. Report errors with actionable fixes. Use for "perses lint", "validate perses", "check dashboard", "perses validate". Do NOT use for plugin schema testing (use perses-plugin-test).
SAP Converged Cloud Go coding conventions extracted from sapcc/keppel and sapcc/go-bits PR reviews. Enforces architecture patterns, library usage rules, error handling conventions, testing patterns, and anti-over-engineering principles. Use when working in sapcc/* repos, when code imports github.com/sapcc/go-bits, or when targeting SAP CC code review standards. Do NOT use for general Go projects without sapcc dependencies.
Run Python quality checks with ruff, pytest, mypy, and bandit in deterministic order. Use WHEN user requests "quality gate", "lint", "verify code quality", "check python", or "pre-commit check". Use for pre-merge validation, CI/CD gating, or comprehensive code quality reports. Do NOT use for single-tool runs (run tool directly), debugging runtime bugs (use systematic-debugging), refactoring (use systematic-refactoring), or architecture review.
Statistical rule discovery through measurement of Go codebases: Count patterns, derive confidence-scored rules, produce Style Vector fingerprint. Use when analyzing codebase conventions, extracting implicit coding rules, profiling a repo before onboarding or PR automation. Use for "analyze codebase", "find coding patterns", "what conventions does this repo use", "extract rules", or "codebase DNA". Do NOT use for code review, bug fixes, refactoring, or performance optimization.
Perses datasource lifecycle management: create, update, delete datasources at global, project, or dashboard scope. Supports Prometheus, Tempo, Loki, Pyroscope, ClickHouse, and VictoriaLogs. Uses MCP tools when available, percli CLI as fallback. Use for "perses datasource", "add datasource", "configure prometheus perses", "perses data source". Do NOT use for dashboard creation (use perses-dashboard-create).
Identify and fix common testing mistakes across unit, integration, and E2E test suites. Use when tests are flaky, brittle, over-mocked, order-dependent, slow, poorly named, or providing false confidence. Use for "test smell", "fragile test", "flaky test", "over-mocking", "test anti-pattern", or "skipped tests". Do NOT use for writing new tests from scratch (use test-driven-development), refactoring architecture (use systematic-refactoring), or performance profiling without a specific test quality symptom.