Loading...
Loading...
Found 597 Skills
Merge Gitea/Forgejo pull requests — all merge styles, auto-merge, mark WIP ready, and branch cleanup.
Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff. Use when the user asks "how do I review this", "summarize the changes", "what should I look at", or wants to understand a PR in under two minutes.
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.
Use when creating or updating a PR in the kimi-code repository: how to write each section of the PR template concisely so that reviewers can easily understand it, including the "Behavior Changes and Affected Users" table.
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.
Turn an idea, tweet, or task into a skill in the Paperclip skills catalog (packages/skills-catalog). Use when asked to FIND or MAKE a skill and publish it as a bundled/optional catalog skill: research prior art, reference or author it, add examples, regenerate the manifest, open a PR.
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.
Brings the checked-out PR up to date after checking its intent against base changes. MODERNIZE rebases, re-runs checks, and force-pushes with a lease; REWORK or CLOSE stops. Use when the user says "modernize this PR", or when the user explicitly asks to bring a PR up to date or rebase it, or when landing-prs or watching-authored-prs calls it on a conflict. Never infer from a behind branch alone.
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).
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an
Git best practices for commit messages and branch workflow. Use when: - Writing, reviewing, or advising on a git commit message - Advising on branching strategy, merging, or rebasing - Setting up or explaining a team Git workflow - Preparing or reviewing a pull request - Resolving or advising how to avoid merge conflicts - Any task involving git history, linear history, or PR hygiene
Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.