Loading...
Loading...
Found 2,776 Skills
Analyse a repository to identify its focus, technology stack, and labels, then search for and apply appropriate shields.io badges to markdown files.
Prepare branch for code review by building context, identifying issues, and suggesting improvements
High-level workflows for managing work using Fizzy cards — start, work on, complete, and delegate cards using the Fizzy CLI.
Build CoinFund-branded web presentations as self-contained HTML files. Supports static (print/PDF) and dynamic (keyboard nav, transitions) modes. Outputs a single versionable HTML file with optional PDF export via Puppeteer. Trigger on: 'web deck', 'web slides', 'html presentation', 'web presentation', or any request for a browser-based slide deck.
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any provider (Codex, Gemini, GPT, Claude, etc.). Use after creating a handoff or when ready to get an AI code review.
Efficiently bring upstream NanoClaw updates into a customized install, with preview, selective cherry-pick, and low token usage.
Visualize planned changes before implementation. Use when reviewing plans, comparing before/after architecture, assessing risk, or analyzing execution order and impact.
Tracked lightweight execution with composable rigor flags for tasks between a typo fix and a full feature. Plan + execute with optional --discuss, --research, and --full flags to add rigor incrementally. Use for "quick task", "small change", "ad hoc task", "add a flag", "extract function", "small refactor", "fix bug in X". Do NOT use for multi-component features, architectural changes, or anything needing wave-based parallel execution — those are Simple+ tier.
Agent skill for swarm-pr - invoke with $agent-swarm-pr
기존 기능의 암묵지를 명세서로 변환하여 as-is Context Pack(주제별 문서 폴더)을 생성하는 스킬. "기능 문서화", "기존 기능 분석", "as-is 정리", "docs/기능별설명 생성" 키워드로 트리거. 신규 기능 Spec이 필요하면 peach-gen-spec을 사용한다.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
This skill should be used when a QA engineer wants to test or verify a completed task, run through acceptance criteria, check Gherkin scenarios against the implementation, record pass/fail results, or sign off on a ticket before merge. Triggers on phrases like "verify task