feat(skill): add deferred-critical-comments pass and reply/resolve pe… - #13
Merged
Conversation
…rmission Introduce a per-comment classification step (3.5) in the resolve-comments kernel that separates "deferred" (critical/large/scope-changing) comments from "normal" in-place edits, then handles normal items first and walks the deferred bucket sequentially in a new Step 4b. For each deferred item the user picks a workflow (SDD, Brainstorming, plan mode, just-do-it, or skip) based on which design skills are visible in the current adapter. Add a one-time-per-project Reply/Resolve permission stored in the existing pr-comments-resolver-platform memory (values: a = post & resolve, b = post only, c = none) and apply it uniformly across Step 4, Step 4b, and the no-code-change path. Add a short clarification routine that suppresses redundant questions when the answer is implied by prior turns. Two new adapter placeholders (skill-availability, classify-confirm) ship with snippet files for all five adapters. persistence-step.md is extended with the new memory field and a back-compat note for older memories. Build smoke test and validate.py assert string presence and placeholder substitution; a manual integration walkthrough is recorded in progress.md.
…olve preferences - Documented new deferred-critical-comments pass, classification process, and workflow options in the README. - Added details about the one-time Reply/Resolve permission and its integration into all comment resolution paths. - Updated CHANGELOG with added features and memory persistence details.
github-actions
Bot
added
the
documentation
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
1 participant
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.
…rmission
Introduce a per-comment classification step (3.5) in the resolve-comments
kernel that separates "deferred" (critical/large/scope-changing) comments
from "normal" in-place edits, then handles normal items first and walks
the deferred bucket sequentially in a new Step 4b. For each deferred item
the user picks a workflow (SDD, Brainstorming, plan mode, just-do-it, or
skip) based on which design skills are visible in the current adapter.
Add a one-time-per-project Reply/Resolve permission stored in the existing
pr-comments-resolver-platform memory (values: a = post & resolve,
b = post only, c = none) and apply it uniformly across Step 4, Step 4b,
and the no-code-change path. Add a short clarification routine that
suppresses redundant questions when the answer is implied by prior turns.
Two new adapter placeholders (skill-availability, classify-confirm) ship
with snippet files for all five adapters. persistence-step.md is extended
with the new memory field and a back-compat note for older memories.
Build smoke test and validate.py assert string presence and placeholder
substitution; a manual integration walkthrough is recorded in progress.md.