From 3d3350c14e55dcfd462656bf0b7308bfee204713 Mon Sep 17 00:00:00 2001 From: codevibesmatter Date: Sun, 19 Apr 2026 11:43:33 -0400 Subject: [PATCH 1/2] feat(skills): create gh issue in kata-close research branch Research mode previously ended with "no issue update". Close now creates a follow-up issue capturing summary, findings, and follow-ups, linked back to the research doc. Makes research output discoverable and actionable outside the research doc itself. Co-Authored-By: Claude Opus 4 --- batteries/skills/kata-close/SKILL.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/batteries/skills/kata-close/SKILL.md b/batteries/skills/kata-close/SKILL.md index 2fd101b..12aa763 100644 --- a/batteries/skills/kata-close/SKILL.md +++ b/batteries/skills/kata-close/SKILL.md @@ -84,7 +84,27 @@ gh issue comment {issue_number} --body "{comment_body}" Commit and push only. Tests are not required for research mode — skip step 2. -No PR creation, no issue update. +No PR creation. + +Create a GitHub issue to capture the research findings and any follow-up work: + +```bash +gh issue create \ + --title "{research_title}" \ + --body "## Summary +{research_summary} + +## Findings +{key_findings} + +## Follow-up +{followup_items} + +Research doc: {research_doc_path}" \ + --label research +``` + +Use the research document's title and top-level summary for `{research_title}` and `{research_summary}`. Link the created issue number back in the commit message or as a follow-up comment if needed. ### If in planning mode From 60a07487cba19fd886fadc789e4a2a07760316a8 Mon Sep 17 00:00:00 2001 From: codevibesmatter Date: Sun, 19 Apr 2026 11:45:46 -0400 Subject: [PATCH 2/2] docs(skills): drop hardcoded research label, gate on label existence `gh issue create --label research` fails in repos without that label. Remove the flag from the example and document the safe pattern: verify label exists via `gh label list --search`, apply only if present, or add post-hoc via `gh issue edit --add-label`. Co-Authored-By: Claude Opus 4 --- batteries/skills/kata-close/SKILL.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/batteries/skills/kata-close/SKILL.md b/batteries/skills/kata-close/SKILL.md index 12aa763..a3a246a 100644 --- a/batteries/skills/kata-close/SKILL.md +++ b/batteries/skills/kata-close/SKILL.md @@ -100,12 +100,19 @@ gh issue create \ ## Follow-up {followup_items} -Research doc: {research_doc_path}" \ - --label research +Research doc: {research_doc_path}" ``` Use the research document's title and top-level summary for `{research_title}` and `{research_summary}`. Link the created issue number back in the commit message or as a follow-up comment if needed. +Labels are not applied automatically — `gh issue create --label ` fails when the label doesn't exist in the target repo. If the project has a `research` (or similar) label and you want to apply it, verify it exists first: + +```bash +gh label list --search research --json name --jq '.[].name' +``` + +Only add `--label ` to the create command above if the label is present. Otherwise, add labels after the fact with `gh issue edit --add-label ` once the repo has them. + ### If in planning mode Run spec validation: