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
- MarcusJellinghaus/mcp-tools-pyedited, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- MarcusJellinghaus/mcp-tools-py★ 2188% same
Wrote their own version · 0
None found.
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.
In this repository22 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- commit_pushSkill
- discussSkill
- implementation_approveSkill
- implementation_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement-directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- issue_requirementsSkill
- issue_updateSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- pr_comment_triageSkill
- rebaseSkill
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
- Distinctive: line 16
Use a clear, descriptive title
- Distinctive: line 18
Use markdown formatting for better readability
- Distinctive: line 23
If the feature should be based on a branch other than the default (main/master), include:
- Very specific: line 36
Important: Before specifying a base branch, verify it exists: Call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", …
- Very specific: line 37
Call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", "origin", "<branch-name>"].
- Distinctive: line 39
If no base branch is needed, omit this section entirely.
- Very specific: line 41
Create the issue: call mcp__mcp-workspace__github_issue_create with title and body.
- Distinctive: line 43
If no prior discussion context is found, respond: "No discussion context found.
≈ “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.
Files
Create GitHub Issue
Based on our prior discussion, create a GitHub issue.
Instructions:
- Extract the issue title and body from the conversation context
- Use a clear, descriptive title
- Include relevant details from our discussion in the body
- 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."
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
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.

