pstack: bump to 0.6.0 and refresh README#104
Merged
Merged
Conversation
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.
bumps pstack from 0.5.0 to 0.6.0 for the recent batch of skill changes (build-the-lever now defaults to building a rerunnable tool for any non-trivial work, architect designs from the caller's usage first, interrogate gained a code-quality lens applied by all four reviewer models, replies are framed for the consumer and the maintainer, Opus references updated to 4.8). README updated to match: reply framing line, architect row, interrogate row.
Note
Low Risk
Version bump and documentation-only README changes; no runtime or application code paths are modified in this diff.
Overview
Release 0.6.0 bumps
plugin.jsonfrom0.5.0to0.6.0and aligns the README with the latest skill behavior (the substantive skill edits ship outside this diff).The poteto-mode flow now documents that step 4 produces replies framed for the consumer and the maintainer, not only “unslopped” text. A ## skills heading was added before the skills table.
README rows were tightened for
/architect(caller’s usage first, then types and module shape) and/interrogate(four models plus a strict code-quality lens).Reviewed by Cursor Bugbot for commit 2b5d046. Bugbot is set up for automated code reviews on this repo. Configure here.