agentleFS
Sign inStart free
WaniWani-AIWaniWani-AI/sdk/.agents/skills/pull-request/SKILL.md

pull-request

Skill18 starsChanged 5 months agoMITView on GitHub

Ensure a Linear ticket exists, then create and push a GitHub pull request for the latest commit — assigned to the author and linked so Linear auto-closes it. Use when the user runs /pull-request or asks to open a PR, create a pull request, push their branch as a PR, or "PR this".

  • Commits and pushes

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use issue-campaign, contracts and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • samchonSkill

    issue-campaign

    Defines the default solo repository-wide issue campaign for typia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo Self-Review, and repeated rediscovery until a full clean round. Use for broad audits, many issue candidates, or repeated issue-to-pull-request campaigns unless the user explicitly requests parallel or multi-agent execution; do not use for one already-defined issue or an ordinary pull request.

    Also in 3 projects that use this

  • AnthropicSkill

    contracts

    Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says, which contracts have a clause, what changed between amendments, or any question that needs reading and citing across a set of contract files. The corpus must be on the local filesystem (see README).

    Also in 3 projects that use this

  • mfang0126Skill

    development

    Full-stack development workflow skill. Guides the complete cycle from understanding requirements to shipping code via PR with Preview validation.

    Also in 3 projects that use this

  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 4 projects that use this

  • VercelSkill

    gh-stack

    Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

    Also in 3 projects that use this

  • carapace-shSkill

    git

    Use when working with Git — object model, references, index, branching, merging, rebasing, remotes, diffs, config, hooks, worktrees, submodules, and plumbing commands. Triggers on: "git", "git branch", "git commit", "git merge", "git rebase", "git checkout", "git stash", "git reset", "git submodule", "git worktree", "git blame", "git bisect", "git reflog", "git hooks", "git config".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a GitHub pull request immediately using the following rules:

    line 8
  2. Very specific:

    Check whether a Linear ticket is already associated with this work.

    line 12
  3. Distinctive:

    If a ticket identifier is found, reuse it - no need to create a new one.

    line 13
  4. Distinctive:

    If NO ticket is found, create one with the Linear MCP:

    line 14
  5. Very specific:

    Create the issue with a concise title derived from the latest commit message, assigned to "me".

    line 16
  6. Very specific:

    Verify the assignment took effect (the created issue's assignee should be the current user).

    line 19
  7. Distinctive:

    Ensure we're on the correct branch (not main/master).

    line 24
  8. Very specific:

    Use gh pr create --assignee @me to create the PR and auto-assign it to the user.

    line 25
  9. Distinctive:

    Use the latest commit message as the PR title.

    line 26
  10. Distinctive:

    Keep the PR title simple - just use the commit message as-is.

    line 31
  11. Distinctive:

    Do not add extra formatting or emoji to the title.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a Pull Request

Create a GitHub pull request immediately using the following rules:

Step 1: Ensure a Linear ticket exists (do this BEFORE pushing)

  1. Check whether a Linear ticket is already associated with this work. Look for a ticket identifier (e.g. WAN-123) in the current branch name and in the latest commit message(s).
  2. If a ticket identifier is found, reuse it - no need to create a new one.
  3. If NO ticket is found, create one with the Linear MCP:
    • Do NOT hardcode an email. The Linear MCP is authenticated as the person running this skill, so assign the issue with assignee: "me" - this is the reliable team-safe way to assign to the current user. (Git/GitHub email may differ from the Linear email, so matching by email is unreliable; only fall back to list_users matching if "me" is unavailable.) Use list_teams to resolve the team.
    • Create the issue with a concise title derived from the latest commit message, assigned to "me".
    • Set its state to "In Progress".
    • Capture the returned ticket identifier (e.g. WAN-123) and its URL.
    • Verify the assignment took effect (the created issue's assignee should be the current user); if it didn't, retry the assignment explicitly with save_issue.

Step 2: Create the PR

  1. Push any uncommitted changes first if needed. If there are uncommitted changes, commit them first before creating the PR.
  2. Ensure we're on the correct branch (not main/master).
  3. Use gh pr create --assignee @me to create the PR and auto-assign it to the user.
  4. Use the latest commit message as the PR title.
  5. Make sure the Linear ticket is referenced so Linear links and auto-closes the PR: include the ticket identifier (e.g. WAN-123) either in the branch name or in the PR description body. If the ticket identifier is NOT already in the branch name, the PR body MUST contain a line Closes WAN-123 (using the real identifier). If it is already in the branch name, leave the body empty.

Important:

  • Keep the PR title simple - just use the commit message as-is.
  • Do not add extra formatting or emoji to the title.
  • The Linear ticket check/creation MUST happen before pushing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free