Loading...
Loading...
Found 3,127 Skills
Generate changelogs, release notes, and migration guides from git history. Parse conventional commits. Use for releases. NOT for git ops (git-workflow) or doc sites (docs-steward).
Design, optimize, and debug CI/CD pipelines. GitHub Actions and GitLab CI patterns. Use for pipeline work. NOT for infrastructure provisioning (infrastructure-coder) or app code.
Use when creating, repairing, querying, auditing, or migrating Obsidian-native git KBs with raw/wiki layers. NOT for docs sites or generic notes.
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.
Sets up GitHub repositories, links Vercel projects, and collects credentials via a secure local web form. Installs environment variables directly into Vercel and GitHub without shell leakage.
Review one or all open pull requests in saadeghi/daisyui using the GitHub MCP server and isolated base-versus-PR verification. Use when Codex must fact-check a daisyUI PR, verify that it solves its stated problem or linked issue, test concrete regression risks, explain developer experience before and after, decide whether it is safe to merge, and write a concise report under tmp/pr/. Base every report statement on linked sources, inspected code, or observed command output; never invent claims, risks, results, or confidence deductions.
Use when asked to find skill opportunities in a codebase, audit a repo for automatable workflows, decide what skills to write, or mine git history and existing automation for recurring multi-step procedures worth turning into Claude Code skills.
Generate and maintain a project's reader-facing documentation in-repo — getting-started, how-to guides, architecture overview, runbooks — with every command verified against the code, in four modes: init, update, audit, and an opt-in publish that mirrors the set to the GitHub wiki. Use when the user says "write docs for this project", "document this repo", "update the docs", "our docs are stale", "write a runbook", "write a getting-started guide", "architecture overview", "sync the docs to the GitHub wiki", or "/wikikit". Not an agent handoff, and not the glossary or ADRs.
Use when adding changelog entries, creating release notes, cutting releases, and publishing them to GitHub.
Drafts and validates Git commit messages that follow the Conventional Commits specification and use Chinese as the primary commit language. Use when writing, reviewing, or fixing commit messages; choosing types or scopes; marking breaking changes; adding bodies or issue footers.
Set up Claude Code hooks to intercept dangerous Git commands (push, reset --hard, clean, branch -D, etc.) before execution. Use this when users want to prevent destructive Git operations, add Git security hooks, or block git push/reset in Claude Code.
(NS) Sync existing GitLab issues with local planning and execution — milestone, RF labels, status transitions, assignee, estimates, spent time. Use during implementation when tasks link to GitLab issues or after plan-version-from-gitlab sync — not for creating new issues (use mcp-gitlab-usage). Always use atomic set_issue_labels and three-step status cycle. Read mcp-gitlab-usage for tool contracts.