Loading...
Loading...
Found 2,050 Skills
Write Markdown that people actually read — READMEs, docs, PR bodies, issue bodies and comments, release notes, changelogs. Covers GitHub-flavored extras (alerts, collapsible sections, task lists, mermaid), prose that leads with the point instead of burying it, and a README skeleton.
Star the ax repo, file an issue / bug report, or fork-and-open-a-PR against github.com/Necmttn/ax on the user's behalf, by shelling out to the `gh` CLI. Triggers when the user says "star ax", "star the repo", "I want to support ax", "report this as an ax bug", "file an ax issue", "open an issue on ax", "this looks like an ax bug", "I want to contribute to ax", "fix this in ax", "open a PR against ax", or after an unhandled ax error when the user wants to report it. Acts only on an explicit user request - proactive star prompting is handled deterministically by the CLI (`ax star`), not this skill. Confirms before any account-mutating action (never stars without an explicit yes); falls back to a plain GitHub URL when `gh` is missing or unauthenticated. Do NOT auto-trigger on unrelated GitHub work or other repos.
Build or resync a private reviewer that learns your GitHub code-review style.
End-to-end GitHub issue workflow: analyze the issue, plan and implement, verify with available tests/build/lint and an optional live observation, simplify, audit the tests it added, attack the change with parallel adversarial reviewers and fix what they find, trim comments and artifacts, then choose a push / PR / merge endgame — holding the merge while Copilot and other automated reviewers report, and answering and resolving their threads. The lifecycle's git and GitHub writes are delegated to `issue-flow`, the review threads to `pr-review`.
Use when a finalized non-[DRAFT] GitHub issue needs an implementation plan published for execution in a separate fresh context. Not for refining the specification or for a one-file, one-behavior change.
Use when brainstorming a feature or change whose spec should land in a GitHub issue instead of a docs/ file — including starting, pausing, and resuming a brainstorm across multiple sittings. The issue is created early as a [DRAFT] and becomes the durable spec; implementation happens separately later. Triggers include "brainstorm this into an issue", "spec it out as a GitHub issue", "file an issue for this feature", "continue/resume brainstorming issue
Assess one specified GitHub issue for implementation readiness, ask blocking questions, and update it after approval.
masseater/typescript-template から作ったリポジトリの GitHub 側を gh で設定する。Actions の secrets、Actions による PR 作成の許可、PR を作れる人の制限と auto-merge、既定ブランチのルールセットを揃える。テンプレートから新しいリポジトリを作ったとき、GitHub の設定を揃え直すときに使う。ほかのリポジトリでも使えるが、その場合は適用する手順をユーザーに確認する。
Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.
Create custom GitHub Actions (composite, Docker, or JavaScript). Use when building reusable actions, creating custom workflow steps, or packaging logic for distribution. Trigger words include "create action", "custom action", "build action", "composite action", "Docker action".
Open a draft pull request on GitHub. MUST use when you want to create/open a PR.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.