搜索与研究
incubate-tool
Graduate a LET spec into a new org repository. Use when creating a tool repo, when a requirement is ready to leave the board, or when the user runs /incubate-tool.
linux-engineering-tools · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add linux-engineering-tools/community --skill incubate-tool技能说明
name: incubate-tool description: Graduate a LET spec into a new org repository. Use when creating a tool repo, when a requirement is ready to leave the board, or when the user runs /incubate-tool.
Incubate a tool
A new repository is a last resort. Do this only after a maintainer decision on a request for comments (RFC). Spell out a term on first use in the new README, or link community TERMS.md.
Gates (all required)
- Requirement issues exist, in capability language,
ip:clean - Public spec under
specs/<name>/(problem, standards, CLI, tests, license) - Upstream check documented: existing project named, asked on its Forge URL (see
catalog/README.md), declined or wrong home - RFC issue approved by a maintainer
- If GUI: desktop contract in the spec (
agents/skills/omarchy-desktop/SKILL.md): Wayland plus a user-editable keybinding file
If any gate is missing, stop and file or finish that work here. Do not create the repo.
New repo
- Under
github.com/linux-engineering-tools/<name> - Public, Apache License 2.0 (unless matching a required upstream license for a fork/patch repo — prefer not forking)
- Copy
AGENTS.mdpointer pattern,CODE_OF_CONDUCT.md, DCO PR template,SECURITY.mdwith private reporting enabled - Enable Issues only for that tool’s bugs. New capabilities still go to
community - CLI with
--help, stable exit codes, JSON where lists are returned - Headless tests and fixtures in-tree
- No CLI named
let(shell builtin). Uselet-<tool>or similar
Do not add the new codebase to community.
After create
Link the RFC and spec from the new README. Set the RFC issue to status:incubating. Do not announce a replacement for a named commercial product.