lime-governance
Govern Lime legacy cleanup, fact-source convergence, current/compat/deprecated/dead classification, and guardrails.
npx skills add limecloud/lime --skill lime-governance --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 治理与立即替换 先读取 `internal/aiprompts/governance.md`(仓库事实源)。 如果需要快速找入口,再看 `internal/aiprompts/README.md`。 如果任务涉及: - Electron IPC / App Server / legacy adapter / Bridge / mock / 前端 API 网关:再读 `internal/aiprompts/commands.md` - GUI 壳 / Workspace / 页面主路径:再读 `internal/aiprompts/quality-workflow.md` 如果当前任务本身是在更新治理规则,先改仓库里的 `internal/aiprompts/governance.md`,再视需要同步本 skill 的参考文件。 ## Fast Path 用户问“结论 / 复核 / 是否能删 / 是否 dead”时,先用 `3-8` 行给结论和关键证据;不要自动展开成全量 inventory、文档清理或长 checklist。只有用户要求继续治理、修文档、补守卫或实现,才进入完整工作流。 目录级旧实现如果同时满足:已不在构建 / workspace manifest 中、当前工作树已物理删除或 staged delete、已有 current owner 承接、边界守卫能防回流,可直接按目录级 `dead / deleted / forbidden-to-restore` 判定;不要求逐文件证明业务语义无价值。`internal/exec-plans/**`、旧路线图和 git history 里的旧路径默认是历史 evidence,不是 current owner 残留。 ## Agent / Codex 固定口径 处理 Agent、`agent_runtime_*`、Agent tools、runtime loop、session/thread、MCP、Skills 或 native tool 迁移时,先按 `/Users/coso/Documents/dev/rust/codex` 做能力对照: - Codex 有的能力:迁入 Lime current owner,并让 App Server、前端 GUI、Evidence / replay / analysis 或运行时主链至少一条真实消费链用起来。 - Codex 没有的 Agent-only 能力:默认 `dead / deleted / forbidden-to-restore`,同步清 vendor 实现、catalog alias、前端 normalization/display/summary、测试正向断言和 active checklist。 - 同名不同义必须按 Codex 语义重建
- Fast Path
- Agent / Codex 固定口径
- 何时使用
- Codex 工作流
- 0. 路线图任务先防跑偏
- 1. 先盘点,再修改
- 2. 定义事实源并分类
- 3. 优先做减法
- 4. 主链路和旁路一起治理
- 5. 用仓库守卫封住老路
- 6. 做最贴边界的验证
- Codex 约束
- 输出要求
npm run governance:legacy-report npm run test:contracts npm run verify:local npm run verify:gui-smoke
What does the lime-governance skill do?
Govern Lime legacy cleanup, fact-source convergence, current/compat/deprecated/dead classification, and guardrails.
How do I install it?
Run `npx skills add limecloud/lime --skill lime-governance --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From limecloud/lime, a repository with 1,464 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
