chore(dx): tighten github skill — issue creation flow + Copilot review docs#80
Merged
Conversation
After filing #79 with only labels and getting flagged, tighten the docs so the agent matches the full convention (title + body + labels + milestone + type) by default. Replaces the 'prompt about milestone' step with 'apply the active milestone; only ask if multiple are active' so this works in autonomous-mode runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Docs-only update tightening the agent's GitHub issue creation workflow so that new issues are filed with a complete set of metadata (title, body, labels, milestone, and type) by default, rather than as label-only stubs.
Changes:
- Rewrites the Creation Flow in
.claude/skills/github/SKILL.mdinto a tighter checklist that bundles labels into the initialgh issue createcall and adds explicit milestone/type steps withSquishMark 1.0as the default milestone. - Updates
CLAUDE.mdto point at the github skill's full creation flow and explicitly forbid label-only issues.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CLAUDE.md | One-line reinforcement directing new-issue creation through the github skill's full flow. |
| .claude/skills/github/SKILL.md | Condenses 5-step flow into a checklist requiring title + body + labels + milestone + type, defaulting milestone to SquishMark 1.0. |
Add a Copilot Code Review section to references/pull-requests.md covering: the working reviewer identifier (copilot-pull-request-reviewer[bot] with brackets), the two correct waiting signals (copilot_work_started timeline event for 'work started', then the reviews API for 'review submitted'), the ~60s lag before inline comments populate, and how to reply / re-request. The Copilot reviewer is a GitHub App posting reviews directly — it does NOT produce a workflow run or a check, so gh run list and gh pr checks won't help. The signals live on the issue timeline and reviews APIs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
x3ek
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two related tightenings of the
githubskill, no code changes.1. Issue creation flow (
.claude/skills/github/SKILL.md,CLAUDE.md)After filing #79 with only labels (no milestone, no type), reshape the creation flow so the agent files complete issues by default:
SquishMark 1.0) instead of prompting, so it works in autonomous-mode runs.CLAUDE.mdpointing at the skill's full flow.2. Copilot Code Review docs (
.claude/skills/github/references/pull-requests.md)New section covering how to request a Copilot review and wait for it. Surfaced after I incorrectly reported "no workflow correlates to a Copilot review" — there isn't an Actions run or check-run, but there IS a
copilot_work_startedtimeline event on the PR, performed by appcopilot-pull-request-reviewer. The reference now documents:copilot-pull-request-reviewer[bot]with brackets — other variants 422 or get silently dropped).copilot_work_startedtimeline event (work started), then the reviews API (review submitted), then a ~60s lag for inline comments.🤖 Generated with Claude Code