agentleFS
rioX432rioX432/agent-witness/.claude/skills/pr/SKILL.md

pr

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Create a pull request for the current branch using the project's PR template

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a pull request for the current branch.

    line 22
  2. Very specific:

    Check if the current branch has a remote.

    line 27
  3. Distinctive:

    Look up the related GitHub Issue from branch name or commit messages

    line 29
  4. Very specific:

    Read .github/pull_request_template.md if it exists

    line 30
  5. Very specific:

    Create PR with gh pr create, include changelog entry and audit attachment in body

    line 33
  6. Very specific:

    Run agent-witness report (no argument: the latest session for this directory).

    line 54
  7. Distinctive:

    Sanitize check (required, human-visible): read the report before attaching.

    line 59
  8. Very specific:

    If agent-witness is not installed or no session was recorded, skip the attachment and note that honestly in the PR body instead of omitting …

    line 75
  9. Distinctive:

    If no issue: omit the number

    line 81
  10. Distinctive:

    No AI stamps, no Co-Authored-By

    line 84
  11. Distinctive:

    Always set base branch explicitly

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

/pr — Pull Request Creation

Create a pull request for the current branch.

Steps

  1. git status and git diff to understand all changes
  2. Check if the current branch has a remote; push with -u if needed
  3. git log and git diff <base>...HEAD to understand ALL commits
  4. Look up the related GitHub Issue from branch name or commit messages
  5. Read .github/pull_request_template.md if it exists
  6. Generate changelog entry from commits (see below)
  7. Generate the session audit attachment (see below)
  8. Create PR with gh pr create, include changelog entry and audit attachment in body

Changelog Generation

From step 3 commits, generate a changelog entry categorized by type:

### Changelog
- **Added**: {new features}
- **Changed**: {modifications to existing features}
- **Fixed**: {bug fixes}
- **Removed**: {removed features}

Include this in the PR body after the description. If a CHANGELOG.md exists in the project root, prepend the entry under the ## [Unreleased] section.

Session Audit Attachment (dogfooding)

Attach the agent-witness record of the work session to the PR body — every PR ships with the evidence of how it was made (Core Value: evidence you can share).

  1. Run agent-witness report (no argument: the latest session for this directory). If it clearly isn't the session that produced this branch (check the tool calls against the diff), pick the right one via agent-witness ls and a selector; if none matches, skip the attachment and say so in the PR body — never attach an unrelated session's record.
  2. Sanitize check (required, human-visible): read the report before attaching. It contains local paths and command lines. Remove or redact anything that must not be public (home-directory usernames are acceptable for this repo; secrets, tokens, or unrelated project paths are not). If in doubt, ask before attaching.
  3. Append it to the PR body inside a collapsed block:
<details>
<summary>Session audit (agent-witness)</summary>

{report markdown}

</details>

If agent-witness is not installed or no session was recorded, skip the attachment and note that honestly in the PR body instead of omitting silently.

Rules

  • Title: #{Issue} {concise description} (under 70 chars)
  • If no issue: omit the number
  • Description: bullet points summarizing changes
  • Other template sections: leave as-is
  • No AI stamps, no Co-Authored-By
  • Always set base branch explicitly
  • Link issues with Closes #XX in body if applicable

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.