Loading...
Loading...
Found 237 Skills
This skill should be used when the user asks to "scan Python code for security issues", "set up Bandit", "configure bandit security linting", "fix bandit warnings", or needs guidance on Python static security analysis with Bandit.
Run quality gates on implemented feature: tests, lint, type checks, and custom validation. Use after /feature-implement completes. Use for "validate feature", "run quality gates", "check feature", or "/feature-validate". Do NOT use for ad-hoc linting or debugging.
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.
Run TypeScript type checking with tsc --noEmit and parse errors into actionable, file-grouped output. Use when validating TypeScript code before commits, after refactors, or when checking for type regressions. Use for "type check", "tsc", "TypeScript errors", "type validation", or pre-commit TypeScript verification. Do NOT use for linting, test execution, runtime errors, or JavaScript-only projects without tsconfig.json.
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.
Review and fix comments containing temporal references, development-activity language, or relative comparisons. Use when reviewing code comments, preparing documentation for release, or auditing inline comments for timelessness. Use for "check comments", "temporal language", "comment review", or "fix docs". Do NOT use for writing new documentation, API reference generation, or code style linting unrelated to comment content.
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
Verify cross-component wiring: exports are imported AND used, real data flows through connections, output shapes match input expectations. Use after /feature-implement, before /feature-validate, or standalone on any codebase. Use for "check integration", "verify wiring", "are components connected", "integration check", or "/integration-checker". Do NOT use for unit test failures, linting, or single-file correctness issues.
Check GitHub Actions workflow status after git push using gh CLI. Reports CI status, identifies failing jobs, and suggests local reproduction commands. Use after "git push", when user asks about CI status, workflow failures, or build results. Use for "check CI", "workflow status", "actions failing", or "build broken". Do NOT use for local linting (use code-linting), debugging test failures locally (use systematic-debugging), or setting up new workflows.
Comprehensive Rust coding guidelines covering ownership, error handling, async patterns, traits, testing, performance, clippy, and documentation. Use when writing new Rust code, reviewing or refactoring existing Rust, implementing async systems with Tokio, designing error hierarchies, choosing between borrowing and cloning, setting up tests or benchmarks, configuring linting, or optimizing performance. Do not use for non-Rust languages or general software architecture unrelated to Rust idioms.
HyperFrames CLI tool — hyperframes init, lint, preview, render, transcribe, tts, doctor, browser, info, upgrade, compositions, docs, benchmark. Use when scaffolding a project, linting or validating compositions, previewing in the studio, rendering to video, transcribing audio, generating TTS, or troubleshooting the HyperFrames environment.
Run local development commands on the Dayuse.com project. Use when starting/stopping Docker, running PHP tests (PHPUnit), frontend tests, linting (PHPStan, CS-Fixer, ESLint), database migrations, Elasticsearch indexing, translations, or any inv task. All commands require pipenv and Docker.