agentleFS
Sign inStart free
openfloconopenflocon/Flocon/.claude/skills/create-pull-request/SKILL.md

create-pull-request

Skill379 starsChanged 28 days agoMITView on GitHub

Use only when the user asks to open a pull request on Flocon. Pushes the branch and creates the PR against main with a conventional title and the repo template. Runs in the Haiku `git-ops` agent: pass the checks already run and their results as arguments.

  • Commits and pushes

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grilling and frontend-design.

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.
  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only run when the user explicitly asks for a PR.

    line 10
  2. Very specific:

    Body: start from .github/PULL_REQUEST_TEMPLATE/pull_request_template.md.

    line 19
  3. Very specific:

    Keep the final /gemini review line.

    line 21
  4. Distinctive:

    No Claude attribution line.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 27 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

Only run when the user explicitly asks for a PR.

Task from the caller: $ARGUMENTS

  1. Check the branch: not main, working tree clean, name follows git-setup (<type>/<feature-kebab>). Otherwise fix it first following .claude/skills/git-setup/SKILL.md.
  2. Local checks: the caller lists the checks from .claude/rules/build-verification.md it ran and their result. If it gives none, run them for the touched area. If the SDK public API or a no-op module changed, also run cd FloconAndroid && ./gradlew :sample:android:assembleDebug :sample:android:assembleRelease. If a check fails, stop and report it. State clearly any check that could not be run.
  3. Check sync: protocol, docs/, MCP docs and README updated per .claude/rules/docs-protocol-sync.md.
  4. Push: git push -u origin <branch>. Never force-push.
  5. Title: same format as a commit, <type>: [AREA] imperative summary (PRs are squash-merged, the title becomes the commit).
  6. Body: start from .github/PULL_REQUEST_TEMPLATE/pull_request_template.md.
    • Under ### Description: what changed and why, and which parts are touched (SDK / Desktop / MCP / docs).
    • Keep the final /gemini review line.
    • No Claude attribution line.
  7. Create (always as a draft, unless the user explicitly asks for a ready-for-review PR): write the body to a temp file, then gh pr create --draft --base main --title "<title>" --body-file <file>.
  8. Report the PR URL and the checks run. The calling session then calls the ccd_pr get_status tool, bind_pr if it doesn't report the PR, and offers Auto-fix. Don't poll CI and don't enable auto-merge unless asked.

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