feat: split Smith skill into task-scoped, directly invocable skills
维护者通常 4 天内回复
@dhl123 已经在做这个了。
开始于 2026年9月10日。
评估
这个 Issue 还没有评估数据。
描述
Summary
Smith is currently exposed as a single smith skill. Every task — policy creation, test generation, policy testing, patching, Regal formatting, deduplication, cross-validation — is routed through one SKILL.md, which reads the user's intent and then delegates to the appropriate guide under opa_policy/ or test_generation/.
This has three costs:
- No direct invocation. There is no way to say "run test generation" as a command. The user has to phrase it as natural language and rely on SKILL.md routing to the right guide.
- The router is a bottleneck. Every new capability means another branch in SKILL.md, and the whole contract loads for even the narrowest task.
The proposal is to split Smith into task-scoped skills, each directly invocable — /smith-test, /smith-policy-creation, /smith-policy-testing, and so on. The underlying smith --flag CLI does not change. This is a restructuring of the skill layer only.
User story
User Story 1
- As a: Smith user who knows exactly which stage I want to run
- I want: to invoke that stage directly as its own skill, e.g. /smith-test
- So that: I don't have to phrase my intent as prose and hope the router dispatches correctly
Acceptance Criteria
Scenario: Invoking a stage direct
- Given the task-scoped skills are installed
- When I invoke /smith-test
- Then the test-generation workflow runs, and no other stage's instructions are loaded
- 主要语言
- Python
- 星标
- 17
- 派生
- 6
- 平均合并
- 4 天 31 分钟
- 30 天内合并 PR
- 16
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
IBM/smith 的其他 Issue
-
security
难度 2/5 1-3 小时 新手友好度 55/100
维护者通常 4 天内回复
-
feat: Support tool scoped security guidance analysis可能重新可做 @iamsreec 于 46 天前认领，目前没有进行中的 PR。 未关闭enhancement
维护者通常 4 天内回复
-
feat: Provenance tracking between requirements, test cases, and policy blocks可能重新可做 @iamsreec 于 51 天前认领，目前没有进行中的 PR。 未关闭enhancement
维护者通常 4 天内回复
-
feat: Organize subskills as graphs可能重新可做 @dhl123 于 51 天前认领，目前没有进行中的 PR。 未关闭enhancement
维护者通常 4 天内回复
-
feat: add vector-based retrieval for threat catalog loading 0.1.3可能重新可做 @iamsreec 于 51 天前认领，目前没有进行中的 PR。 未关闭enhancement
维护者通常 4 天内回复
相似的 Issue
-
SslLibrary crashes with unhandled OSError: port/proto not found on non-standard SSL ports可能已有人在做 @himanchalkaushale 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
OWASP/Nettacker#1884 · 1 条评论 ·
维护者通常 1 天内回复
-
A-connection-core C-enhancement
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
aws-samples/sample-per-model-bedrock#869 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 82/100
fzn0x/watchtower#17 ·