`/effort` 与 `/thinking` 在 `/` 菜单中重复置顶，建议只显示其一
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with BUILTIN_SLASH_COMMANDS and STEP_SLASH_COMMAND_PRIORITY, then inspect the /effort branch in input-dispatch.ts. Update the step-slash-commands and tui-acceptance tests to cover one visible entry while keeping /effort usable as a hidden alias. The work is done when the relevant tests pass and the menu no longer shows both commands.
Written by the indexing model from the issue text.
Description
What do you want to change?
/ 自动补全列表顶部同时钉着 /effort 和 /thinking 两个条目（STEP_SLASH_COMMAND_PRIORITY），但两者打开同一个 thinking level 选择器、都走 handleThinkingCommand，描述也几乎一样。建议菜单只保留一个，/effort 保留为隐藏别名（输入仍然有效），类似 /debug 已有的隐藏命令做法。
Why?
两条功能完全一致、描述相近的命令相邻置顶，容易让人误以为是两种不同的设置（第一次看到会以为一个调 model、一个调推理）；也浪费了一个置顶位。
How?
最小改动：从 BUILTIN_SLASH_COMMANDS 移除 effort 条目，并从 priority 列表去掉它；input-dispatch.ts 中的 /effort 分支保留即可。需要同步更新 step-slash-commands 与 tui-acceptance 相关测试。
如果双入口是有意的 discoverability 设计，也建议至少在 usage.md 写明 /effort 是 /thinking 的别名（目前文档只写了 /thinking）。
- Dominant language
- TypeScript
- Stars
- 471
- Forks
- 42
- Avg merge
- 18h 11m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stepfun-ai/Step-Code
-
area/build bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stepfun-ai/Step-Code#190 · 2 comments ·
Maintainers usually reply within 1 day
-
area/tools bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stepfun-ai/Step-Code#186 · 1 comment ·
Maintainers usually reply within 1 day
-
area/tools bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stepfun-ai/Step-Code#185 · 1 comment ·
Maintainers usually reply within 1 day
-
area/tools bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stepfun-ai/Step-Code#184 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stepfun-ai/Step-Code#179 · 1 comment ·
Maintainers usually reply within 1 day
All issues in stepfun-ai/Step-Code
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
LucasSantana-Dev/Lucky#2637 ·
Maintainers usually reply within 1 day
-
Show the error reference on the error pagePossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
tomjn/coilbox-hub#454 ·
Maintainers usually reply within 1 day
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
icssc/peterportal-client#1224 · 1 comment ·
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day