weekly sync — 2026-05-18#4
Open
norbert-pap wants to merge 1 commit into
Open
Conversation
- gstack #1431: add Unicode safety rule to AskUserQuestion format in all 5 review skills (prod-review, eng-review, design-review, code-review, qa) Never \uXXXX-escape CJK/accented characters; tool pipe is UTF-8-native. https://claude.ai/code/session_01CjLSrTtKATrWPKQevBocKc
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.
Weekly upstream sync — 2026-05-18
Sources checked: 6 (garrytan/gstack, addyosmani/agent-skills, anthropics/skills, VoltAgent/awesome-agent-skills, rohitg00/awesome-claude-code-toolkit, Owl-Listener/designpowers)
Applied changes (1)
gstack #1431 — Unicode safety rule in AskUserQuestion format
prod-review,eng-review,design-review,code-review,qa\u-escaping. Affects any AskUserQuestion call involving project names, strings, or user-facing content with non-ASCII characters. Clean one-line addition, no infrastructure dependencies.Deferred / noteworthy (5)
gstack #1504 — Implementation Tasks synthesis in review skills
plan-ceo-review→ prod-review,plan-eng-review→ eng-review,plan-design-review→ design-review,plan-devex-review(no claudebert equivalent)## Implementation Taskssection to each review skill that emits JSONL task artifacts with schema (component, files, title, priority, effort) to~/.gstack/projects/$SLUG/tasks-{phase}-{datetime}.jsonlforautoplanaggregation.~/.gstack/projects/path are gstack-specific infrastructure. Claudebert already writes test plan artifacts (~/.claudebert/projects/) from eng-review. Porting the concept requires a judgment call on: (a) should claudebert adopt a JSONL task format? (b) what replaces the autoplan aggregator? This is valuable but ambiguous — not a clean text replacement.gstack — AskUserQuestion decision-brief format upgrade
D<N>/ELI10/Stakes/Completeness/pros-cons(✅❌)/Netformat with a 10-item self-check before everyAskUserQuestioncall. Significantly richer than claudebert's current 4-step format.AUTO_DECIDEreferences), the core format is cleanly portable — but the scope/style change is too large to auto-apply without user review. Recommend a dedicated PR.gstack #1512 — EXIT PLAN MODE GATE
ExitPlanModecall in plan-mode review skills, verifying## GSTACK REVIEW REPORTis the file's terminal heading.ExitPlanModecalls.gstack #1442 — Learnings integration in /qa
LEARNINGS_SEARCHmacro to/qawith keyword string"qa testing bug regression flake fixture"for task-shaped memory retrieval.LEARNINGS_SEARCHis a gstack/gbrain macro with no claudebert equivalent. Would require building or wiring a memory retrieval system first.addyosmani/agent-skills #164 — interview-me skill
Sources with no relevant activity this week
Generated by Claude Code