chore(skills): agent-executable follow-up comments in td-pr-contributor-review#516
Merged
cidrblock merged 1 commit intoJul 20, 2026
Merged
Conversation
…or-review Teach maintainers to leave a single P0/P1 brief (problem, why, what, acceptance, non-goals, verification, done definition) so another agent can execute review follow-ups without re-deriving intent from chat.
3 tasks
sudhirverma
approved these changes
Jul 20, 2026
github-project-automation
Bot
moved this from Review
to Done
in 🧰 devtools project board
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
2 participants
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
Extend
td-pr-contributor-review(v1.2.0) with guidance for writing agent-executable maintainer comments when a contributor PR needs work and another session (human or agent) will land the fixes.Motivated by the follow-up brief pattern used on redhat-developer/abbenay#83: a single ordered comment with P0/P1 items, problem/why/what/acceptance per item, explicit non-goals, verification commands, and a done definition — so the next agent does not re-derive intent from chat.
Supersedes the fork-based PR #515 (same change; reopened as a same-repo PR so
lintcan useBOT_PAT).Changes
Test plan
tox -e lint(prek / codespell / etc.)lintwithBOT_PAT,ackwithchorelabel)