agentleFS
samueltuoyo15samueltuoyo15/Dokugen/.agents/skills/prepare/SKILL.md

prepare

Skill345 starsChanged 39 days agoMITView on GitHub

Inspects full git diff across uncommitted changes and branch commits, then generates ready-to-paste GitHub Issue and PR markdown matching exact repository templates.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. iliasedelkin/jobissimo★ 8same name
    2. 2389-research/git-repo-prep★ 2same name
    3. mik2win/foureyes★ 2same name
    4. Aquilo-Solution-S/tesla-valve★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    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. Very specific:

    Use this skill when the user runs /prepare or requests to prepare an issue and pull request.

    line 8
  2. Very specific:

    Run git log origin/main..HEAD and git diff origin/main...HEAD (or git diff HEAD~N..HEAD if upstream is not set) to review ALL committed …

    line 13

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

Prepare GitHub Issue & PR Generator

Use this skill when the user runs /prepare or requests to prepare an issue and pull request.

Workflow Instructions

  1. Inspect the full branch history and diff:
    • Run git log origin/main..HEAD and git diff origin/main...HEAD (or git diff HEAD~N..HEAD if upstream is not set) to review ALL committed changes on the current feature branch.
    • Also check git status --short and git diff for any remaining uncommitted edits.
    • Combine all committed features, bug fixes, and chores across the entire branch to provide complete, comprehensive context.
  2. Determine whether the branch represents:
    • Feature request (feat: ...): Use the Feature Request template fields (Problem, Proposed solution, Alternatives considered).
    • Bug report (bug: ...): Use the Bug Report template fields (What happened, Steps to reproduce, Where, Additional context).
    • Chore / task (chore: ...): Use the Chore template fields (What needs to change, Why now).
  3. State explicitly which issue template option to choose on GitHub: Feature request, Bug report, or Chore / task.
  4. Provide the exact text to paste into each field of that GitHub Issue form.
  5. Format the Pull Request body based on .github/PULL_REQUEST_TEMPLATE.md.

Output Format

1. GitHub Issue

Template to Choose on GitHub: [Feature request | Bug report | Chore / task]
Title: [type]: [short descriptive title]

For Feature Request:

### Problem
[Describe what is missing or awkward today: the gap]

### Proposed solution
[Describe what was built across the stack]

### Alternatives considered
[Other approaches or notes, or leave blank if standard]

For Bug Report:

### What happened
[What you did, what you expected, what happened instead]

### Steps to reproduce
1. ...
2. ...

### Where
[Package or app affected, e.g. apps/web, apps/server]

### Additional context
[Logs, context, or notes]

For Chore / Task:

### What needs to change
[What needs to change in the codebase]

### Why now
[What prompted this change]

2. GitHub Pull Request

Title: [type]: [short descriptive title]

## Issue

Closes #[ISSUE_NUMBER]

## What changed
- [Concise bullet point 1]
- [Concise bullet point 2]
- [Concise bullet point 3]

## How to verify
1. [Step 1 to test or verify]
2. [Step 2 to test or verify]

## Checklist
- [x] Linked issue was approved before this PR was opened
- [x] `pnpm lint` and `pnpm build` pass locally
- [x] New/changed behavior has been verified
- [x] Docs (README, docs) updated 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.