Problem
The pr-flow skill (.claude/skills/pr-flow/SKILL.md) takes an issue through to a merged PR, but no step tells you to read the issue. That covers the body, and it also covers the comment thread. Step 1 ("Start from an issue") only checks that an issue exists, assigns it and moves its card to In Progress. Every other mention of "comments" in the skill is about PR review comments (steps 7–8). AGENTS.md says only "check the board for the relevant item" before starting work.
Issue comments are often where scope actually changes. A maintainer narrows or widens the ask, rules out an approach, links a related issue, or records a decision the body never got updated with. An agent following the skill as written can branch and implement against the original body alone, and it builds the wrong thing.
Expected
Step 1 of pr-flow tells you to read the issue and every comment on it (gh issue view <N> --comments) before branching, and to treat a later comment that contradicts the body as the current scope. If that scope is still unclear after reading, ask before you start.
Scope
A procedure change, so it goes in the skill, not in AGENTS.md. It edits the skill body only, not its description, so the skill listing budget and trigger evals are unaffected.
Problem
The
pr-flowskill (.claude/skills/pr-flow/SKILL.md) takes an issue through to a merged PR, but no step tells you to read the issue. That covers the body, and it also covers the comment thread. Step 1 ("Start from an issue") only checks that an issue exists, assigns it and moves its card to In Progress. Every other mention of "comments" in the skill is about PR review comments (steps 7–8).AGENTS.mdsays only "check the board for the relevant item" before starting work.Issue comments are often where scope actually changes. A maintainer narrows or widens the ask, rules out an approach, links a related issue, or records a decision the body never got updated with. An agent following the skill as written can branch and implement against the original body alone, and it builds the wrong thing.
Expected
Step 1 of
pr-flowtells you to read the issue and every comment on it (gh issue view <N> --comments) before branching, and to treat a later comment that contradicts the body as the current scope. If that scope is still unclear after reading, ask before you start.Scope
A procedure change, so it goes in the skill, not in
AGENTS.md. It edits the skill body only, not itsdescription, so the skill listing budget and trigger evals are unaffected.