issue-creation
Skill439 starsChanged 7 months agoApache-2.0View on GitHub
Structured workflow for drafting NEW GitHub issues with codebase research, duplicate detection, and testing approach. Always asks clarifying questions and shows the draft for approval before creating. For searching, listing, viewing, or updating existing issues, use the "issues" skill instead.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- svg153/skillstheir own version, first seen Nov 1, 2026
- martinhg/capiko-aitheir own version, first seen Oct 20, 2026
- 0xErwin1/dbfluxtheir own version, first seen Oct 9, 2026
- wazuh/wazuh-dashboard-pluginstheir own version, first seen Oct 8, 2026
- Gentleman-Programming/gentleman-guardian-angeltheir own version, first seen Oct 8, 2026
- AndyTechnologies/my-own-skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use chained-pr, work-unit-commits and 3 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.
joeldevzSkillchained-pr
Split large changes (>400 lines OR >5 slices) into a series of reviewable PRs. Two strategies — stacked-to-main and feature-branch-chain. Prevents the 100-conflict merge disaster.
Also in 3 projects that use this
joeldevzSkillwork-unit-commits
Commit discipline. Each commit is a self-contained, reviewable work unit — code + tests + docs together. Stops the 190-commit PR disaster before it starts.
Also in 3 projects that use this
alex-ilgayevSkillgo-testing
Handles all Golang testing tasks including running tests, writing new tests, and fixing test failures. Follows MCPSpy testing conventions with require for critical assertions and assert for non-critical ones.
Also in 3 projects that use this
- +2 more from joeldevz
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Gentleman-Programming/gentleman-guardian-angel★ 1.2ksame name
- 0xErwin1/dbflux★ 566same name
- wazuh/wazuh-dashboard-plugins★ 534same name
- KemingHe/common-devx★ 10same name
- martinhg/capiko-ai★ 2same name
- svg153/skills★ 1same name
- AndyTechnologies/my-own-skills★ 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 repository29 other files it gives its agents.
- ark/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- a2a-protocolSkill
- Ark AnalysisSkill
- ark-architectureSkill
- ark-controller-developmentSkill
- ark-dependabot-managementSkill
- ark-sdk-developmentSkill
- ark-setup-clusterSkill
- ark-chainsaw-testingSkill
- Ark Dashboard and UI TestingSkill
- ark-documentationSkill
- ark-issuesSkill
- multi-branch-cluster-setupSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- ark-pentest-issue-resolverSkill
- ark-researchSkill
- slack-announcementSkill
- ark-vulnerability-fixerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 16 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
16
Distinctive
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
- Very specific: line 8
Create well-researched, problem-focused GitHub issues for mckinsey/agents-at-scale-ark.
- Distinctive: line 12
Use when the user asks to create an issue, report a bug, request a feature, or track work.
- Distinctive: line 16
Follow these steps in order.
- Distinctive: line 20
ALWAYS ask clarifying questions before doing any research or drafting.
- Distinctive: line 29
Do NOT proceed to Step 2 until the user has answered your questions.
- Distinctive: line 33
Before writing anything, investigate the relevant code:
- Distinctive: line 39
Use Grep, Glob, Read, and the Explore agent as needed.
- Distinctive: line 45
Search existing issues thoroughly in the main repo:
- Distinctive: line 63
If a duplicate exists in either repo, tell the user and link to it instead of creating a new issue.
- Distinctive: line 64
If related issues exist in either repo, note them as dependencies or references in the new issue.
- Distinctive: line 96
ALWAYS present the full draft (title + body) to the user before creating the issue.
- Distinctive: line 100
Do NOT create the issue until the user approves.
- Distinctive: line 104
Only after the user approves the draft:
- Distinctive: line 120
Always ask clarifying questions first: Never skip straight to research or drafting.
- Distinctive: line 124
Research first: Every issue must include codebase research findings.
- Distinctive: line 125
No duplicates: Always check existing issues before creating.
- Distinctive: line 127
Always add "needs grooming" label: Every issue created by this skill gets this label.
“Common” is measured: kept by at least 6 in 10 of the 7 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.
Files
Issue Creation
Create well-researched, problem-focused GitHub issues for mckinsey/agents-at-scale-ark.
When to use this skill
Use when the user asks to create an issue, report a bug, request a feature, or track work. This skill enforces a research-first approach before creating any issue.
Process
Follow these steps in order. Do NOT skip steps.
Step 1: Ask clarifying questions
ALWAYS ask clarifying questions before doing any research or drafting. Never assume you have enough context. Use AskUserQuestion to gather:
- What exactly is the problem? (Get specifics, not just a vague description)
- Who is affected and how severely?
- How is the problem reproduced? (for bugs)
- What is the motivation or trigger? (for features)
- Is there any urgency or deadline?
- Are there any constraints the user already knows about?
Do NOT proceed to Step 2 until the user has answered your questions. If the user's initial description is detailed, still confirm your understanding by summarizing back and asking if anything is missing.
Step 2: Research the codebase
Before writing anything, investigate the relevant code:
- Find the files, modules, and components involved
- Understand the current behavior and architecture
- Identify the scope and blast radius of the problem
- Note relevant file paths and code references
Use Grep, Glob, Read, and the Explore agent as needed. Include key findings in the issue's Context section so reviewers can orient themselves without re-doing the research.
Important: The purpose of research is to understand the problem's scope and surface area — NOT to prescribe a solution. Do not let research findings leak into prescriptive implementation steps. Knowing which files are involved helps the implementer orient; telling them what to change in those files anchors them on a path that may be wrong.
Step 3: Check for duplicates and dependencies
Search existing issues thoroughly in the main repo:
gh search issues --repo mckinsey/agents-at-scale-ark "<keywords>" --json number,title,state,labels --jq '.[] | "\(.number) [\(.state)] \(.title)"'
gh issue list --repo mckinsey/agents-at-scale-ark --state open --json number,title,labels --jq '.[] | "\(.number) \(.title)"' | grep -i "<keyword>"If the issue relates to the marketplace (observability, community services, Phoenix, Langfuse, optional service integrations, or anything in the marketplace repo), also search and research mckinsey/agents-at-scale-marketplace:
gh search issues --repo mckinsey/agents-at-scale-marketplace "<keywords>" --json number,title,state,labels --jq '.[] | "\(.number) [\(.state)] \(.title)"'
gh issue list --repo mckinsey/agents-at-scale-marketplace --state open --json number,title,labels --jq '.[] | "\(.number) \(.title)"' | grep -i "<keyword>"Also research the marketplace codebase for relevant patterns, existing implementations, and architectural context using the gh CLI or web fetch against https://github.com/mckinsey/agents-at-scale-marketplace. Include marketplace findings in the issue Context section when relevant.
- If a duplicate exists in either repo, tell the user and link to it instead of creating a new issue.
- If related issues exist in either repo, note them as dependencies or references in the new issue.
Step 4: Draft the issue
Use this template:
## Problem
[Clear description of what is broken, missing, or suboptimal. Focus on the problem, NOT the solution.]
## Context
[Codebase research findings: relevant files, current behavior, architecture context. Include file paths.]
## Impact
[Who is affected? What breaks or degrades? How severe is this?]
## Related Issues
- #N — [brief description of relationship]
## Testing Approach
- [How to verify the problem is fixed]
- [What test types are appropriate: unit, integration, e2e]
- [Edge cases to cover]Step 5: Show the draft and ask for edits
ALWAYS present the full draft (title + body) to the user before creating the issue. Use AskUserQuestion to ask:
- Does the draft look good?
- Any sections to add, remove, or reword?
Do NOT create the issue until the user approves. If they request edits, apply them and show the updated draft again.
Step 6: Create the issue
Only after the user approves the draft:
gh issue create --repo mckinsey/agents-at-scale-ark \
--title "<type>: <concise problem description>" \
--body "$(cat <<'EOF'
<issue body from step 5>
EOF
)" \
--label "needs grooming"Title must use conventional commit prefix: feat:, fix:, docs:, chore:, refactor:, etc.
Rules
- Always ask clarifying questions first. Never skip straight to research or drafting. Confirm understanding before proceeding.
- Focus on the problem, not the solution. The issue author's job is to be the expert on the problem. Never propose a design, implementation approach, or specific code changes unless the user explicitly asks for one.
- Research informs scope, not implementation. Codebase research belongs in the Context section to help the implementer orient. It must NOT become prescriptive implementation steps. Knowing which files are involved is useful context; telling the implementer what to change in those files anchors them on a path that may be wrong.
- No uninformed specificity. Implementation details written by someone without deep codebase knowledge create false confidence and anchoring bias. A vague-but-accurate issue is more useful than a specific-but-wrong one.
- Research first. Every issue must include codebase research findings.
- No duplicates. Always check existing issues before creating.
- Testing approach required. Suggest how to verify the fix/feature.
- Always add "needs grooming" label. Every issue created by this skill gets this label.
- Link dependencies. Reference related issues when they exist.
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.

