Loading...
Loading...
Found 2,031 Skills
Use when one ready GitHub issue or one explicitly confirmed conversation specification needs a repository-aware implementation plan for a later implementation workflow.
Use this skill when testing a RevenueCat Android integration. Covers the RevenueCat Test Store (test_ API key prefix, in dialog Success/Fail/Cancel choice), mockk based unit testing with an interface wrapper around Purchases, and a GitHub Actions CI pattern. Avoids Google Play sandbox for day to day test iteration.
Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.
Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
Sets up GitHub repositories, links Vercel projects, and collects credentials via a secure local web form. Installs environment variables directly into Vercel and GitHub without shell leakage.
CI/CD pipelines for .NET applications. Covers GitHub Actions and Azure DevOps YAML pipelines with build, test, publish, and deploy stages. Load this skill when setting up continuous integration, automated testing, deployment workflows, or when the user mentions "CI/CD", "pipeline", "GitHub Actions", "Azure DevOps", "workflow", "deploy", "build pipeline", "publish", "NuGet push", "release", or "continuous integration".
Review one or all open pull requests in saadeghi/daisyui using the GitHub MCP server and isolated base-versus-PR verification. Use when Codex must fact-check a daisyUI PR, verify that it solves its stated problem or linked issue, test concrete regression risks, explain developer experience before and after, decide whether it is safe to merge, and write a concise report under tmp/pr/. Base every report statement on linked sources, inspected code, or observed command output; never invent claims, risks, results, or confidence deductions.
Generate and maintain a project's reader-facing documentation in-repo — getting-started, how-to guides, architecture overview, runbooks — with every command verified against the code, in four modes: init, update, audit, and an opt-in publish that mirrors the set to the GitHub wiki. Use when the user says "write docs for this project", "document this repo", "update the docs", "our docs are stale", "write a runbook", "write a getting-started guide", "architecture overview", "sync the docs to the GitHub wiki", or "/wikikit". Not an agent handoff, and not the glossary or ADRs.
Use when adding changelog entries, creating release notes, cutting releases, and publishing them to GitHub.
build a repo-local skill and install a matching iterated coding-agent GitHub Actions workflow, prompt, memory file, and reference templates
Publicar uma versão estável do Specsfy CLI a partir do monorepo promovaweb/specsfy, mantendo pacote, executável, CHANGELOG.md, commit, tag e GitHub Release coerentes. Use quando a pessoa pedir para lançar ou retomar uma versão do CLI. Não use para pré-releases nem apenas para atualizar o CLI de um consumidor.
Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after `bm ci collect` prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for `bm ci publish`.