pick-issue
Skill11 starsChanged 13 days agoApache-2.0View on GitHub
Choose and claim one FinFocus roadmap issue, implement it through the repository workflow, prepare a pull request, and release the claim. Use when the user invokes pick-issue or asks to pick up a roadmap issue, optionally with an issue number.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read and follow the shared command before starting.
- Very specific: line 13
Treat any issue number or other arguments in the user's invocation as inputs to the command.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Pick a Roadmap Issue
Read and follow the shared command
before starting. That file is the maintained workflow; resolve its relative
links from .claude/commands/ and run its shell commands from the repository
root unless a step changes directories.
Treat any issue number or other arguments in the user's invocation as inputs
to the command. FinFocus's Spec Kit commands use dotted names such as
/speckit.specify. Read the linked command files when no corresponding Codex
skill is available. Map /code-review and /scout to the corresponding
available skills; report unavailable capabilities without claiming to run them.
Apply the current session's instructions and authorization when interpreting Claude-specific tool or permission notes. Loading or migrating this skill alone does not authorize claiming an issue or other external actions.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- shuvamk/openbench★ 2same name
- jamesc/skills★ 0same name
- kompiro/hane★ 0same 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- promote-issueSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- agentic-workflow-designerSkill
- agentic-workflowsSkill
- code-reviewSkill
- jqschemaSkill
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.