Loading...
Loading...
Found 696 Skills
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Applicable when you need to resolve ongoing git merge/rebase conflicts.
Run a bounded, evidence-first audit-fix-review-verify loop on a codebase when the user asks to improve, harden, overhaul, or fix all confirmed defects. Use only with explicit edit authority in a git repository. Do not use for advisory-only reviews, a single narrow bug, or when the worktree is dirty and the owner has not chosen how to preserve it.
Write clear, conventional commit messages with proper type prefixes, scopes, and body content.
Open pull requests in a consistent format. Use when opening or updating a PR, or when follow-up commits leave an open PR's title or body stale.
Generate Conventional Commit messages by inspecting current staged Git changes or using provided staged Git context. Use when asked to write a commit message, summarize staged changes, or classify a change as feat/fix/refactor/docs/test/build/ci/style/perf.
The standard workflow from opening an Issue through branching, implementation, PR, and merge, along with the conventions for Git/GitHub operations. Covers the type(scope) commit message format, how to choose scope, handling of --author, verifying author and committer addresses, prohibiting Co-Authored-By and git add ., squash merging by philtz-organizer-bot through the merge label, checking ahead/behind, and how to write Issue comments and Releases. Use when committing, pushing, creating or switching branches, merging, rebasing, or creating Issues, PRs, comments, and Releases.
Delegate a coding task to Muse Code (`muse`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Muse — phrasings like "have Muse do X", "delegate this to Muse", "run it through Muse", or "use Muse to implement/fix/refactor" — or wants to run a queue of coding tasks through Muse while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. It applies only when the user wants that separate `muse exec` implementer run: if you are Muse yourself and the user simply asks you to write the code, do it directly. DO NOT USE for tasks small enough to do inline.
You MUST use this when anyone - you, a subagent, or the user - is about to state that work is done, fixed, ready, or mergeable, and before the commit that completes it, a merge, opening a pull request, or a handoff report, including work that has no plan. Covers every promise behind the claim - spec criteria, plan tasks, journal entries, accepted review fixes, and the caller's words - proven with fresh checks on the current tree and given one verdict, without editing code. Not for fixing failures (implement) or reviewing (cr-request). Replaces devflow verification-gate.
Implement a chosen contribution in a fork of an open-source project: verify the user's fork already exists (stop and ask the user to fork if it does not), strictly follow the upstream repository's conventions (CONTRIBUTING.md, AGENTS.md, CLAUDE.md, PR template, commit and sign-off format), work on a branch of the fork without opening any fork PR, write equivalence-first tests, run the upstream CI/CD checks locally before pushing (the fork will not run them), sign commits per the upstream DCO/CLA convention, and post the PR body — built from the upstream PR template — in a markdown pasteable format on the Multica issue. In review iterations (the PR is already open and a maintainer left review comments), address only the explicit requests on the same fork branch and post a pasteable PR comment per PR in the same fenced-markdown format; PR discussions — replies, resolutions, ambiguous asks — are left for the humans. Use whenever a Multica issue asks to "work on the contribution", "implement <candidate> in <owner/repo>", "prepare the branch for <repo>", "turn the scouted contribution into a PR-ready diff", or to "address the review comments on <PR>" — even if the issue only names the target repo and the change to make.
Splits a large change into stacked pull requests with GitHub's gh stack CLI. Use when the user says "stack PRs" or "create a PR stack", or when a change is too big to review as one PR, has dependent parts, or overlaps the same author's open PRs, or when creating, updating, syncing, merging, or recovering a gh stack stack.
Review and resolve open review feedback on a pull request against its upstream repository, then keep the branch in sync without rewriting history. Use when asked to "review my PR", address PR/review comments, respond to reviewer feedback, resolve review threads, or sync a feature branch with upstream before review. Covers: resolving the upstream remote (from git remote -v when not configured), challenging vs. fixing each comment, replying to and resolving threads with gh, and detecting/handling a branch that is behind upstream main (conflict check, user confirmation, no force-push).