execute-issue
Skill2 starsChanged 47 days agoAGPL-3.0View on GitHub
Execute an already-scoped software issue or explicitly approved implementation task through repository investigation, focused implementation, validation, self-review, commit preparation, and pull-request handoff. Use when asked to implement, fix, advance, continue, or complete work whose intended outcome is already defined. Coordinate temporary independent subagents when separate investigation materially reduces work; keep sequential work in one flow. Do not use to invent or decompose unclear product scope.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- moiznoorani/skillstheir own version, first seen Oct 11, 2026
- lbedner/aegis-stacktheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- lbedner/aegis-stack★ 146same name
- moiznoorani/skills★ 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.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-issues-and-epicsSkill
- diagnose-ci-failureSkill
- handle-security-advisorySkill
- maintainer-inboxSkill
- repository-healthSkill
- review-pull-requestSkill
- upstream-compatibilitySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
35 rules. About 0 are common, 34 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈34
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.