agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/github-pr-creation/SKILL.md

github-pr-creation

Skill0 starsChanged 8 months agoMITView on GitHub

用于创建 GitHub PR：当用户要开 PR、提交评审、检查是否 ready for PR、生成 PR 标题/描述或整理待提交项时使用。Combine with `git-commit` and `verification-before-completion` when 提交前还需要收口；Prefer `github-pr-merge` when the task is 合并已有 PR。

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify the final state before marking the work ready.

    line 16
  2. Distinctive:

    Keep examples generic, privacy-safe, and portable across hosts.

    line 21
  3. Distinctive:

    Do not use when review feedback still materially blocks submission.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

github-pr-creation

Intent

  • 用于创建 GitHub PR：当用户要开 PR、提交评审、检查是否 ready for PR、生成 PR 标题/描述或整理待提交项时使用。Combine with git-commit and verification-before-completion when 提交前还需要收口；Prefer github-pr-merge when the task is 合并已有 PR。

Default operating pattern

  1. Collect the current diff, review feedback, or readiness question.
  2. Separate objective issues from style preferences and duplicated concerns.
  3. Recommend concrete code changes, replies, or follow-up checks.
  4. Verify the final state before marking the work ready.
  5. Summarize remaining risks and ownership clearly.

Pack fit

  • Included in: engineering-workflow
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not use when review feedback still materially blocks submission.

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