Loading...
Loading...
Found 1,622 Skills
Create pull requests using GitHub CLI with proper templates and formatting
Add line-specific review comments to pull requests using GitHub CLI API
Turn the current conversation into a spec (Problem, Solution, User Stories, Decisions) and publish it as a GitHub issue. Validates a feature before any code is written.
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing review feedback, resolving threads, looping bot reviews, checking approvals, querying PR data, configuring Copilot reviews, or configuring gh/glab read-only allowlists. Not for git commits (git-commit), CI/CD status (git-ci), local pre-push CodeRabbit CLI reviews (coderabbit), or general git ops
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
Apply the canonical GitHub issue and pull-request label set to a repository.
Add a GitHub Actions workflow that posts code-size and cost statistics — lines of code, per-language breakdown, complexity, and a COCOMO "what would this cost to build" estimate — as a sticky comment on every pull request, using scc. Use when you want a per-PR code-stats or "worth of the codebase" comment, to show LOC / language breakdown or an estimated development cost/effort on PRs, to set up scc (Sloc Cloc and Code) in CI, to post or upsert a single self-updating bot comment from GitHub Actions, or to change the COCOMO salary/currency. Covers fork-PR token limits, runner architecture, version pinning, and comment pagination.
Deterministic issue-relationship graph over GitHub native sub-issues + dependencies — compute the ready set / parent-rollup candidates / close-kick targets as pure calculation (scripts, no LLM judgment), write real edges when creating spin-off issues, and mutually exclude terminal actions across parallel agents via claim-comment fencing. Called by issue-sweep (candidate injection), issue-review (edge writing + rollup), and the future agent:ready producer routine.
Deploy browser games to here.now (default), GitHub Pages, or other hosting. Use when deploying a game, setting up hosting, or publishing a game build. Do NOT use for local development servers (use npm run dev).
Review Renovate bot PRs that update GitHub Actions dependencies. Verifies supply chain integrity by checking pinned commit SHAs against upstream tagged releases, reviews changelogs for breaking changes, and confirms compatibility with existing workflow configurations. Use when a Renovate PR updates GitHub Actions in .github/workflows/.
Push projects to GitHub with three automatically determined modes: **First-time Push** (large file scanning → generate .gitignore → git init → create repo via gh → push), **Daily Update** (commit + push), **Version Release** (tag + create Release, optional attached download files). Core principle: Safety First: Must scan for large files and sensitive files before pushing, better to ask one more question than push something that shouldn't be pushed. Triggered when users say "push to GitHub", "git push", "upload to GitHub", "commit and push", "release version", "create release", "create tag", "/git-push". Not applicable for: Planning which features go into which version number (use issue-pool—this skill only handles tagging pre-determined version numbers), complex git operations like rebase/cherry-pick/resolving conflicts/modifying history/rolling back (use git commands directly, this skill does not cover these), self-testing and acceptance before code is completed.
Triages a repository's open GitHub issues and pull requests via the gh CLI. Optionally reviews and merges ready PRs — incrementally merging passing automated/bot PRs and maintainer-approved ones, and spawning review subagents for never-reviewed ones — then closes already-resolved issues with comments citing the resolving PR or commit, cross-links issues with their pending fix PRs, and assigns local-only priority and change-size estimates for everything outstanding. Use when triaging, grooming, or reviewing a repository's open issues and PRs.