Loading...
Loading...
Found 2,519 Skills
Use this skill for direct work with GitHub: inspecting remote source or repository state, searching hosted code, invoking GitHub CLI (`gh`) commands such as `gh search` and `gh api`, or performing another operation against GitHub. Do not use it for ordinary local Git work unless the user explicitly requests `gh`. Do not use it for tasks limited to viewing or interacting with GitHub in a browser.
Use when a push went up or a PR opened, or when waiting on a PR's reviews, merge, or CI, or on a branch tip's CI, so a daemon the session owns delivers the events as messages instead of polls.
MUST be used whenever writing or replying to anything on GitHub - issues, pull requests, discussions, review threads. Enforces technical brevity, bans AI execution diaries, report bloat, bot watermarks, and em dashes.
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.
Attach image and video media to GitHub pull request descriptions or issue and pull request comments with the GitHub CLI on GitHub.com and GHE.com.
Pin the GitHub Actions a repository uses to full commit SHAs and add a check that keeps new ones pinned. Use when hardening CI against a compromised or retagged action, or when a workflow uses an action by tag or branch.
Replace a GitHub Actions schedule trigger with a Crontap HTTP dispatch while keeping the workflow, runner, and logs on GitHub. Use when a user needs a timezone-aware external clock or wants to avoid scheduled-workflow drift.
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
current release-driven Operating ModelをGitHub Issues / Pull Requestsへmaterializeし、release sprint / dependency / review / durable delivery stateを扱う時に使用する。
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's backlog backend (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the backlog, triage labels, or domain docs.
Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.
pr-to-video workflow - a GitHub pull request (URL like github.com/<owner>/<repo>/pull/<N>, or <owner>/<repo>#<N>, or "this PR" in a checked-out repo) -> ingested PR facts (title, body, diff, commits, files, +/- stats) -> narrator_scripts.json + audio (voice + BGM) + section_plan.md -> code-diff / before-after / impact explainer video. Input is a CODE CHANGE. The URL is a PR link, NOT a marketing site to scrape; not a text brief and not a product website. For a non-PR input (product site, general website, topic text), see /hyperframes-read-first.