Loading...
Loading...
Found 265 Skills
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Provides CI/CD pipeline configuration using GitHub Actions for Golang projects. Covers testing, linting, SAST, security scanning, code coverage, Dependabot, Renovate, GoReleaser, code review automation, and release pipelines. Use this whenever setting up CI for a Go project, configuring workflows, adding linters or security scanners, setting up Dependabot or Renovate, automating releases, or improving an existing CI pipeline. Also use when the user wants to add quality gates to their Go project.
Complete QA, playtesting, and code quality team for game development. Use when evaluating player experience, fun factor, game feel, code quality, test coverage, refactoring, performance testing, or build validation. Covers playtesting methodologies, UX research, unit/integration/e2e testing, code review, linting, accessibility, and continuous quality assurance. Triggers on requests for testing, QA, playtesting, code review, refactoring, bug tracking, or quality validation.
Generate Makefiles with testing, linting, formatting, and automation targets for new projects.
Use when a workflow, recipe, or capability needs to be packaged as an agent skill, or when an existing skill needs scaffolding, validation, linting, or evals. Covers requests to build, create, generate, scaffold, check, or evaluate a skill: a folder holding SKILL.md, scripts, tests, a task graph, CI, and eval cases. Applies even when the request says playbook, runbook, or reusable workflow instead of skill.
Use when the user wants to create, generate, or set up a GitHub Actions workflow. Handles CI/CD pipelines, testing, deployment, linting, security scanning, release automation, Docker builds, scheduled tasks, and any custom workflow for any language or framework.
The foundational knowledge distillation pattern for building and maintaining an AI-powered Obsidian wiki. Based on Andrej Karpathy's LLM Wiki architecture. Use this skill whenever the user wants to understand the wiki pattern, set up a new knowledge base, or needs guidance on the three-layer architecture (raw sources → wiki → schema). Also use when discussing knowledge management strategy, wiki structure decisions, or how to organize distilled knowledge. This is the "theory" skill — other skills handle specific operations (ingesting, querying, linting).
Modern Python development with uv, ruff, mypy, and pytest. Use when: - Writing or reviewing Python code - Setting up Python projects or pyproject.toml - Choosing dependency management (uv, poetry, pip) - Configuring linting, formatting, or type checking - Organizing Python packages Keywords: Python, pyproject.toml, uv, ruff, mypy, pytest, type hints, virtual environment, lockfile, package structure
Knowledge base for designing, reviewing, and linting agentic AI infrastructure. Use when: (1) designing a new agentic system and need to choose patterns, (2) reviewing an existing agentic architecture ADR or design doc for gaps/risks, (3) applying the lint script to an ADR markdown file to get structured findings, (4) looking up a specific agentic pattern (prompt chaining, routing, parallelization, reflection, tool use, planning, multi-agent collaboration, memory management, learning/adaptation, MCP, goal setting, exception handling, HITL, RAG, A2A, resource optimization, reasoning techniques, guardrails, evaluation, prioritization, exploration/discovery). All rules and guidance are grounded in the PDF "Agentic Design Patterns" (482 pages).
Build and publish npx-executable CLI tools using Bun as the primary toolchain with npm-compatible output. Use when the user wants to create a new CLI tool, set up a command-line package for npx execution, configure argument parsing and terminal output, or publish a CLI to npm. Covers scaffolding, citty arg parsing, sub-commands, terminal UX, strict TypeScript, Biome + ESLint linting, Vitest testing, Bunup bundling, and publishing workflows. Keywords: npx, cli, command-line, binary, bin, tool, bun, citty, commander, terminal, publish, typescript, biome, vitest.
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 pre-merge validation checklist for Python/React pull requests. Use before approving or merging any PR. Covers code quality checks (linting, formatting, type checking), test coverage requirements, documentation updates, migration safety, API contract compatibility, accessibility compliance, bundle size impact, and deployment readiness. Provides a systematic checklist that ensures nothing is missed before merge. Does NOT cover security review depth (use code-review-security).