agentleFS
Sign inStart free
jeremymcsjeremymcs/skills/create-issue/SKILL.md

create-issue

Skill8 starsChanged 6 months agoMITView on GitHub

Create a single post-mortem GitHub issue and pull request from completed work in the current session. Use when the user wants to turn the contribution just completed into a tracking issue, commit or push the work, and open a PR without decomposing it into multiple implementation tickets.

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use native-nostalgia-stack, software-engineering-excellence and 10 more.

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

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • frostneySkill

    software-engineering-excellence

    Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.

    Also in 3 projects that use this

  • withpiperSkill

    roadmap-review

    Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.

    Also in 3 projects that use this

  • GoogleSkill

    implement-issue

    Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    create-release

    Use when creating a new ASO release, including pre-checks, release notes generation, draft GitHub release creation, documentation updates, and ROADMAP changes.

    Also in 4 projects that use this

  • MicrosoftSkill

    update-pr

    Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 13

    Distinctive

    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:

    Use this skill after a contribution is complete and the user wants a lightweight issue plus PR created from the current session.

    line 10
  2. Distinctive:

    Read the current conversation for the user's goal and what changed.

    line 17
  3. Distinctive:

    If the repo has a contribution or PR template, follow it.

    line 19
  4. Distinctive:

    Use the project issue tracker already configured for the repository.

    line 25
  5. Distinctive:

    If no tracker is configured or authentication is missing, stop and say what is blocked.

    line 26
  6. Distinctive:

    If changes are uncommitted, stage only the intended files, commit them, and push a focused branch.

    line 28
  7. Distinctive:

    If the work is already committed on a branch, push that branch.

    line 29
  8. Distinctive:

    Do not push directly to the default branch unless the user explicitly requested it.

    line 30
  9. Distinctive:

    Default to a draft PR unless the user asks for ready-for-review.

    line 34
  10. Distinctive:

    Keep this to one issue and one PR for the completed contribution.

    line 83
  11. Distinctive:

    Do not invent requirements, labels, milestones, or assignees.

    line 84
  12. Distinctive:

    Do not rewrite unrelated history or include unrelated files.

    line 85
  13. Distinctive:

    If the session context is insufficient to describe the work accurately, ask one targeted question.

    line 86

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

Use this skill after a contribution is complete and the user wants a lightweight issue plus PR created from the current session.

This is not a planning or decomposition skill. Do not split work into multiple slices unless the user asks.

Workflow

  1. Gather the completed-work context.
    • Read the current conversation for the user's goal and what changed.
    • Inspect git status -sb, recent commits, and the relevant diff.
    • If the repo has a contribution or PR template, follow it.
  2. Draft one issue.
    • Title the issue as the completed contribution, not as a future investigation.
    • Body should explain what was done, why it matters, and how it was verified.
    • Include follow-up work only if it is real and not speculative.
  3. Publish the issue.
    • Use the project issue tracker already configured for the repository.
    • If no tracker is configured or authentication is missing, stop and say what is blocked.
  4. Prepare the PR.
    • If changes are uncommitted, stage only the intended files, commit them, and push a focused branch.
    • If the work is already committed on a branch, push that branch.
    • Do not push directly to the default branch unless the user explicitly requested it.
  5. Open the PR.
    • Link the issue with Closes #NUMBER or the tracker's equivalent.
    • Summarize the change and verification.
    • Default to a draft PR unless the user asks for ready-for-review.
  6. Report the result.
    • Provide the issue URL, PR URL, branch, commit, and checks run.

Issue Body

## Summary

Describe the completed contribution in 1-3 sentences.

## Why

Explain the reason this work was useful.

## What changed

- Change 1
- Change 2
- Change 3

## Verification

- Check or command that passed
- Manual verification, if applicable

## Pull request

Added after the PR exists.

PR Body

## Summary

- Change 1
- Change 2

Closes #NUMBER

## Verification

- [ ] Check or command
- [ ] Manual verification, if applicable

Guardrails

  • Keep this to one issue and one PR for the completed contribution.
  • Do not invent requirements, labels, milestones, or assignees.
  • Do not rewrite unrelated history or include unrelated files.
  • If the session context is insufficient to describe the work accurately, ask one targeted question.

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