agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-workspace/.claude/skills/issue_create/SKILL.md

issue_create

Skill49 starsChanged 2 days agoMITView on GitHub

Create a new GitHub issue from discussion context

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use a clear, descriptive title

    line 16
  2. Distinctive:

    Use markdown formatting for better readability

    line 18
  3. Distinctive:

    If the feature should be based on a branch other than the default (main/master), include:

    line 23
  4. Very specific:

    Important: Before specifying a base branch, verify it exists: Call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", …

    line 36
  5. Very specific:

    Call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", "origin", "<branch-name>"].

    line 37
  6. Distinctive:

    If no base branch is needed, omit this section entirely.

    line 39
  7. Very specific:

    Create the issue: call mcp__mcp-workspace__github_issue_create with title and body.

    line 41
  8. Distinctive:

    If no prior discussion context is found, respond: "No discussion context found.

    line 43

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

Create GitHub Issue

Based on our prior discussion, create a GitHub issue.

Instructions:

  1. Extract the issue title and body from the conversation context
  2. Use a clear, descriptive title
  3. Include relevant details from our discussion in the body
  4. Use markdown formatting for better readability

Link related issues. If the issue belongs to an epic or design doc, or has dependencies, list them near the top and in a ## Dependencies / references section — the epic, design doc, dependencies, and any curated sibling issues worth reading. Add a short "read these first" note when they're essential. Omit for standalone issues.

Optional: Base Branch If the feature should be based on a branch other than the default (main/master), include:

### Base Branch

<branch-name>

Use cases:

  • Hotfixes based on release branches
  • Features building on existing work
  • Long-running feature branches

Important: Before specifying a base branch, verify it exists: Call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", "origin", "<branch-name>"].

If no base branch is needed, omit this section entirely.

Create the issue: call mcp__mcp-workspace__github_issue_create with title and body.

If no prior discussion context is found, respond: "No discussion context found. Please discuss the feature or bug first before creating an issue."

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.