Add a response-style setting (normal | concise)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start by trying the proposed concision rule in ~/.claude/CLAUDE.md, as the issue's next step requests. If that is not enough, trace how /setup-gstack stores model role settings and how the plugin's SessionStart hook adds rules to the main chat. Decide the open questions about minimum length, exceptions, and an escape hatch; done means a normal or concise setting works as described without changing subagent output.
由索引模型根据 Issue 内容生成。
描述
Problem
Agent replies are often much longer than they need to be. Reading them takes a lot of effort. The goal is the smallest reply that gets the point across, with more detail only when asked.
Idea
Add a response-style setting to the gstack config: normal or concise.
- Set it through
/setup-gstack, like the model roles. - When it's
concise, a pluginSessionStarthook adds the/brovoice rules to the main chat. Subagents keep their normal output. conciserule: answer first, plain words, no jargon, expand only when asked.
Open questions
-
What counts as "minimum"? One line, answer plus a few bullets, or a hard word cap like
/ketchup's 150 words? -
Exceptions. Draft rule: cut the prose around the content, never the content. Keep these in full:
- errors: the exact error, then one line on what it means
- text you'll copy or run: commands, code, file paths, config, URLs
- confirmations before risky actions: what will be deleted, pushed or overwritten
- drafts you asked for: PR bodies, messages, issue text
- numbers behind a decision: the figure and its source
Code reviews are not exempt. Questions to the user are left to a future grilling skill. Plans should probably become artifacts (a markdown file, a GitHub issue) instead of chat replies. That needs its own design.
-
Escape hatch: is "tell me more" enough, or add something explicit like
/more?
Next step
Try a concision rule in ~/.claude/CLAUDE.md first. Build this only if that isn't enough.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 3 小时 33 分钟
- 30 天内合并 PR
- 13
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
gregogun/gstack 的其他 Issue
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
ready-for-human
难度 4/5 3-5 天 新手友好度 43/100
维护者通常 1 天内回复
-
ready-for-agent
难度 3/5 1-2 天 新手友好度 56/100
维护者通常 1 天内回复
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
cloudscape-design/components#5184 ·
维护者通常 2 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 75/100
JarX-Concepts/react-native-platform-components#130 ·
维护者通常 1 天内回复
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILL未关闭area: backend bug priority: low
难度 2/5 1-3 小时 新手友好度 83/100
snapotter-hq/SnapOtter#3773 ·
维护者通常 1 天内回复
-
ai-driven-qa ux-audit
难度 2/5 1-3 小时 新手友好度 78/100
linagora/twake-contacts-frontend#386 ·
维护者通常 1 天内回复
-
git: README should state plainly that without --repository every reachable repository is in scope未关闭documentation server-git v2
难度 1/5 1-3 小时 新手友好度 84/100
modelcontextprotocol/servers#5225 ·
维护者通常 1 天内回复