Loading...
Loading...
Found 2,521 Skills
Draft and update bug issues using a bug-focused structure, repository-valid labels, and explicit publish confirmation before GitHub mutation.
CI/CD: GitHub Actions workflows, parallel sharding, flaky quarantine, junit XML/Allure, coverage gates
Pull all file comments from the current GitHub pull request and address them by making code changes.
Create or update GitHub Actions workflows (ci, test, release, e2e) based on project type detection
Generate structured video transcripts from local files or video URLs using Gemini Files API. Use when a GitHub or Linear tracker item, comment, or attachment includes a screen recording, .mov, .mp4, or tracker-hosted video and you need a <video-transcripts> block instead of hand-written notes.
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".
Review and triage pull requests on GitHub and Forgejo, including Codeberg, with first-class replies inside GitHub inline review threads. Use when asked to review a PR, inspect a GitHub PR with gh, respond to code-line feedback in its existing thread, inspect a Forgejo PR with fj or its REST API, analyze CI failures, classify unresolved reviewer feedback, prepare fixes, submit an overall review, or resolve review threads.
GH Actions workflow triggering/monitoring gotchas for any repo with multiple workflows (e.g. APK + AAB builds). Use when a push to main did not seem to trigger a workflow, when only .github/** changed (paths filters skip it, needs manual dispatch), when parallel runs need one cancelled, when a build failed and the job log must be pulled, or when checking run status/artifacts. For the end-to-end Expo APK/AAB build flow use gh-actions-expo-apk-build instead.
Take an open GitHub PR and make it merge-ready on your machine, with a worktree, a base-branch sync, the project running, and a review pack of everything you need to judge it, then merge it once you say so, or service review feedback on a PR you authored. Use when you review the PRs an agent opened overnight, say "pull PR #34 down so I can test it", "check out this PR for QA", "get this PR merge-ready", "merge PR #34", "address the review comments on my PR", "my PR is red, fix the CI", or run "/mergekit".
Explore helpful color utility functions, like RGB to HSL, HEX to RGB, and HSL to HEX, generated with the assistance of GitHub Copilot.
Creates GitHub Pull Requests with existing PR detection, branch pushing, and intelligent title/body generation. Use when user requests to create pull request, open PR, update PR, push for review, ready for review, send for review, get this reviewed, make a PR, share code, request review, create draft PR, submit for review, run /create-pr command, or mentions "PR", "pull request", "merge request", "code review", "GitHub PR", or "draft".
GitHub CLI (gh) command reference. Use when working with GitHub repositories, PRs, issues, actions, `gh api`, or any GitHub operations from the command line.