Loading...
Loading...
Found 587 Skills
Propose improvements to a skill in its canonical repository. Defines how to proceed when work does not follow the skill, when information obtained through Web searches differs from or is newer than the skill's content, or when strictly following the skill's conditions is judged to prevent the best possible result. Includes guidance on not directly editing skills installed in the home directory, routing proposals to the appropriate repository, and Issue title and body templates. Use this when you have questions about a skill's content or want to propose an improvement to it.
Draft Elastic documentation for any feature or feature area, from a doc issue, a product pull request, or raw notes. Enforces the docs-content baseline on every draft — verify against product source at HEAD, find the canonical home, place content once, scope it cumulatively — and reads per-area reference files for local conventions when they exist. Use when picking up a doc issue, documenting a shipped or upcoming feature, or turning engineering notes into a page.
Write a branch's PR body that tells a reviewer how much attention it needs, with a visual summary, harvested evidence and a fresh-context one-way or two-way door call, then put it and an attention label on the branch's PR. Use when a branch is ready for review, when the user says "write the PR body", "update the PR description", "how risky is this PR", or "is this ready to merge", and when another skill closes a branch.
Prevent, detect, and repair AI coding slop and dirty engineering in repositories. Use for planning features, writing code, changing tests, reviewing pull requests, refactoring, hardening CI, debugging regressions, or auditing agent-generated changes. Enforces behavioral contracts, focused diffs, test integrity, repo conventions, security boundaries, and evidence-based completion.
A Git workflow assistant toolkit. Use this skill when the user asks to generate a commit message, commit or push code changes, create or switch branches based on a Chinese description, create or update a PR/MR for a target repository, merge a PR/MR by number and update the main branch, tag a branch with a version and push it, tag an already merged stable branch and create a GitHub/GitLab Release by default (the release phase after pr-merge), slim down the current Git repository into a shallow clone, or pull and categorize GitHub starred repositories. It also handles vague requests such as "write a commit message," "commit this," "create a branch for XX," "open a PR," "merge the PR," "create a tag," "publish a release," "publish a version," "slim down the repository," and "categorize my starred repositories."
Runs the full ds-ship workflow but stops with the pull request ready for a human to merge, and never merges. Use when the user says get it ready, make it mergeable, stop before merge, or /ds-ready.
Analyzes open Dependabot PRs for semver level, CI, breaking changes, and security fixes, then squash-merges approved patch and minor updates one at a time, or only comments @dependabot rebase; supports a dry run. Use when the user explicitly asks to merge, process, or rebase Dependabot PRs. Never infer from green CI, an approved Dependabot PR, or stale or conflicting Dependabot PRs.
Expert guidance for GitHub CLI (gh) - issues, PRs, repos, releases, and GitHub API. Use when working with GitHub, managing issues/PRs, or when user mentions GitHub, PRs, issues, or repos. Preferred over GitHub MCP server for context efficiency.
Perform thorough code reviews following Google's 5-step methodology. Use when reviewing pull requests, change lists, or any code changes to ensure quality, correctness, and maintainability.
Push the current feature branch and open a pull request, ready for review. Use after a ticket's implementation is committed on its own branch — it detects the base branch, pushes, opens the PR with a clear body (summary · what changed · validation status), and returns the URL to hand to a reviewer.
Process reviewer feedback, apply required fixes, and draft replies without unsolicited commits.
GitHub CLI operations via `gh` command. Use when working with GitHub repositories, pull requests, issues, code search, releases, or any GitHub API operation. This skill replaces the GitHub MCP server with direct CLI calls. Triggers on: GitHub, PR, pull request, issue, repo, branch, release, tag, commit, fork, merge, review, gh.