agentleFS
priyanshuchawdapriyanshuchawda/codeaudit/skills/github-issue-pr-workflow/SKILL.md

github-issue-pr-workflow

Skill1 starsChanged 6 months agoMITView on GitHub

Use when generating GitHub issue plans, PR plans, branch names, commit scopes, review checklists, merge guidance, or issue-first workflow guidance.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Create or propose an issue first.

    line 12
  2. Distinctive:

    Use a clean scoped branch.

    line 13
  3. Distinctive:

    Keep commits focused and descriptive.

    line 14
  4. Distinctive:

    No auto-push, branch deletion, remote mutation, or auto-merge without explicit user approval.

    line 35

≈ “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 Issue PR Workflow

Required Flow

  1. Create or propose an issue first.
  2. Use a clean scoped branch.
  3. Keep commits focused and descriptive.
  4. Link the PR to the issue.
  5. List tests run.
  6. Describe security impact and docs impact.
  7. Merge only after clean review and verification.

Branch Names

  • fix/issue-12-api-rate-limit
  • refactor/issue-18-split-security-utils
  • docs/issue-21-evidence-map

PR Body Sections

  • Linked issue
  • Summary
  • Tests run
  • Security impact
  • Docs impact
  • Screenshots when UI changed

No auto-push, branch deletion, remote mutation, or auto-merge without explicit user approval.

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.