Git & VCS
Git operations, commit helpers, branch management
brainstorming
by jkitchin
Structured brainstorming and ideation facilitation using proven creativity techniques. Use when users want to generate ideas, explore solutions, break through creative blocks, or need facilitated ideation sessions. Triggers include requests like 'help me brainstorm,' 'generate ideas for,' 'creative solutions to,' or 'think of alternatives.'
commit-changes
by SamGu-NRX
Clean up, review, validate, and commit a repository's intended changes. Use when asked to commit, make a commit, write a commit message and commit, or finish local changes as a Git commit. Always invoke $deslop across every staged file before drafting the message or running git commit.
babysit
by SamGu-NRX
'Watch a PR or related PR stack until merge or closure, coordinate CI and review fixes, and recommend human review. Use for "babysit #N", "watch this stack", or "keep these PRs green". Never merges.'
Skill: Git Hygiene
by strikersam
If in doubt about a commit, use git diff HEAD~1 to review what it contains
insights
by strikersam
Analytics, heatmaps, and trends from session history. Analyze checkpoint logs, learnings, and git history to surface patterns: which files change most, which steps fail most often, and where to invest in tooling or tests.
Skill: Issue Resolver
by strikersam
Prefer surgical fixes over refactors unless the issue explicitly requests cleanup
safe-exec
by OTTTTTO
Safe command execution for OpenClaw Agents with automatic danger pattern detection, risk assessment, user approval workflow, and audit logging. Use when agents need to execute shell commands that may be dangerous (rm -rf, dd, fork bombs, system directory modifications) or require human oversight. Provides multi-level risk assessment (CRITICAL/HIGH/MEDIUM/LOW), in-session notifications, pending request management, and non-interactive environment support for agent automation.
PR Watch
by OmniNode-ai
Poll GitHub PR for review feedback -- dispatches to node_pr_watch_orchestrator for execution
spec-to-issue
by anyoneanderson
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
trent-chezmoi
by trentshaines
Help with chezmoi dotfile management, ansible playbooks, and syncing configs to the dotfiles repository. Use when modifying configuration files in ~/.config, ~/, ansible playbooks, or other managed locations. ALWAYS prompt the user about syncing to chezmoi after making config changes. Please use this anytime I mention configuration for my computer
trent-fish
by trentshaines
Help with fish shell configuration, aliases, functions, and keybindings. Use when the user asks about shell config, aliases, or when modifying shell behavior. IMPORTANT - Trent uses fish as his primary shell, not zsh.
Release
by OmniNode-ai
Org-wide coordinated release pipeline (STRUCTURAL PLACEHOLDER — node_release performs no git/gh/PyPI I/O today; full handler implementation is pending). Target design bumps versions, pins cross-repo deps, creates PRs, merges, tags, and triggers PyPI publish across all OmniNode repos in dependency-tier order
trent-aerospace
by trentshaines
Help with AeroSpace window manager configuration, keybindings, and workspace management. Use when the user asks about AeroSpace, window management, workspaces, or tiling configurations.
backlog-capture
by osdlc
Capture a stray idea fast: interpret freeform text in-session into a concise headline, an optional body, and inferred tags, then shell out to sdlc backlog create (the deterministic tail) to land it on the rolling backlog-capture PR. Invoked as /sdlc:backlog-capture <text>; --fast takes a single silent shot with no clarifying question.
capability-map
by osdlc
Map out the capability graph for one scope of the project: survey the code (or the product's capability-map table), propose new Capability entities where the map has gaps, enrich existing ones with locations, grain, audience and related links, and report retire candidates. Runs sdlc capability coverage and sdlc capability graph read-only, dispatches one read-only sub-agent per candidate, renders one batched plan for approval, then writes through sdlc capability create / sdlc capability update and opens a PR. Invoke when capabilities are missing, ungraded, unanchored, or when the System page's capability view looks empty for an area. Usage: /sdlc:capability-map <dir C-NNNN areas> [--dry-run] [--auto].
lib-publish-ready
by osdlc
Audit one library package for a first public release. Produces a readiness report (every quality-bar row with evidence and a verdict: pass, gap, blocker, n/a or owner), the evidence for the name, worthwhile, stable, home and API gates, an inventory of the public API, the first public version, a sanitized CHANGELOG draft, owner questions with a recommendation each, and a fix list whose items are tagged safe or needs-decision. Reads the package; never writes inside it. Use it before publishing a library to a public registry such as crates.io or npm, or to re-audit after fixes.
check-pr
by osdlc
"Tend one or more pull requests in a single pass: report their state, rebase them onto their base branch when they are behind or conflicting, and assess and answer new review comments. Fixes worthwhile comments straight away with --fix auto, or proposes the fix and waits for a thumbs-up with --fix ask (the default). Keeps no files of its own and records its answers to review-pr findings on a state ref beside the PR, so it suits a loop such as /loop /check-pr."
backlog-triage
by osdlc
Walk untriaged backlog files in docs/planning/backlog/ and decide what to do with each: promote to task, promote to milestone, close, defer (bump last_reviewed), or leave it for an open PR. Before each decision, checks the item against main: the code it names, merged and open PRs, and existing planning entities, and recommends an action with quoted evidence. Promotion calls sdlc task create / sdlc milestone create directly, or points at existing work that already covers the item, and updates the backlog frontmatter to match. Commits each decision atomically on the current branch, honouring the project's branching conventions.
debug-github-ci
by ericmjl
Debug GitHub Actions and CI failures using gh CLI: watch PR checks, fetch run logs, analyze failures, reproduce locally, and suggest fixes. Use when CI fails, when the user wants to watch or verify CI, or when debugging workflow runs.
gh-cli
by ericmjl
Use GitHub CLI (gh) for common operations like creating PRs, viewing GitHub Actions logs, managing issues, reviewing PRs, and more. Use this when you need to interact with GitHub repositories directly from the command line.
gh-daily-timeline
by ericmjl
Reports your GitHub activity for a specific day using the gh CLI, showing commits, issues, and activity timeline. Use this when you need to review what you accomplished on GitHub for a particular date.
SKILL: Azure Kusto Spark Connector — Release Process
by Azure
Keep CHANGELOG.md in sync on both branches
go-linting
by cxuu
Recommended Go linters and golangci-lint configuration. Use when setting up linting for a Go project or configuring CI/CD.
pr-stats
by osdlc
Summarize a pull request or branch diff beyond GitHub's +/-: lines added and removed by code, comments, blank and prose; a change-category breakdown (added, deleted, renamed, tests, docs, generated, formatting-only, comment-only, logic); dependency and exported-API changes; and the cyclomatic-complexity movers. Use before or after opening a PR, in review, or when asked to "summarize this change", "how big is this PR", "what did this branch actually change", or "add stats to the PR". Optionally writes the table into the PR body. Runs from a bundled script with plain Node, git and gh; needs no other plugin.