← ClaudeAtlas

aiw-issue-creationlisted

Structured process for creating follow-up or spin-off GitHub issues during a task. Use this skill when the agent discovers work outside the current scope that should be tracked. The skill exists to prevent implementation-heavy issues that bias the implementing agent and peg to stale code.
philippe-ths/ai-coding-workflow · ★ 0 · AI & Automation · score 66
Install: claude install-skill philippe-ths/ai-coding-workflow
# Issue Creation Read this file when creating a follow-up or spin-off GitHub issue. ## Before Creating the Issue - Search open issues in the repository for overlap with the proposed issue's intent. - If a potential overlap is found, surface the overlapping issue to the human before proceeding. - Search the codebase for other sites where the same request would apply. A request arrives phrased for the place the human noticed it, which is not always the place it belongs. - Only proceed with creation after the human confirms there is no duplicate. ## When the Request Fits More Than One Site Settle the question by one search now, not by counting how often this request has come up before. Sites that share the shape today are visible in the current session; a count of past occurrences needs memory across sessions and arrives after the divergence it would have prevented. Scope does not move. The issue stays at the site the human named, and the finding lands in the acceptance criteria rather than in a note, because a note is free to ignore and acceptance criteria are what the work is checked against. Bind the criterion to the requested site alone, and state it as a property of the result rather than a design to follow: adopting it at the other sites would not mean rewriting it. Name those sites by path. Sorting is asked for on one list screen, and four list screens share the shape. The issue stays on that screen, and its acceptance says the other four could adopt the result unc