Agent skill · Code Review & Quality

lime-quality-workflow

Choose Lime validation commands for GUI, command/bridge, config, version, and PR-readiness changes.

limecloudgithub.com/limecloudGitHub ↗
codex
Install
npx skills add limecloud/lime --skill lime-quality-workflow --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: .codex/skills/lime-quality-workflow/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,464
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Lime 工程质量 先读取 `internal/aiprompts/quality-workflow.md`（仓库事实源）。 如果需要快速找入口，再看 `internal/aiprompts/README.md`。 如果任务涉及： - Electron IPC / App Server / legacy desktop facade / Bridge / mock / 前端 API 网关：再读 `internal/aiprompts/commands.md` - 新旧并存、兼容层收口、旧入口回流：再读 `internal/aiprompts/governance.md` - GUI 续测、页面交互验证：再读 `internal/aiprompts/playwright-e2e.md` 如果当前任务本身是在更新工程质量规则，先改仓库里的 `internal/aiprompts/quality-workflow.md`，再视需要同步本 skill 的参考文件。 ## Fast Path 用户问“结论 / 复核 / 是否能删 / 是否 dead”时，先用 `3-8` 行给结论和关键证据；不要自动升级成 `verify:local`、`test:contracts`、GUI smoke 或全量质量矩阵。只有用户要求继续实现、修文档、补守卫、提交前验证，或改动已经真实触达 GUI / 命令 / bridge / 配置边界时，才进入完整质量工作流。 目录级旧实现若已脱离构建 / workspace manifest、当前工作树已物理删除或 staged delete、已有 current owner 承接，且边界守卫能防回流，可直接按目录级 `dead / deleted / forbidden-to-restore` 判定；不要求逐文件证明业务语义无价值。`internal/exec-plans/**`、旧路线图和 git history 里的旧路径默认是历史 evidence，不是当前质量缺口。 ## 何时使用 当任务涉及以下任一问题时，使用本 skill： - 不确定这次改动最少该跑哪些校验 - 改了 GUI 壳、DevBridge、Workspace、前端主路径 - 改了 Electron IPC、App Server JSON-RPC、legacy desktop facade、Bridge、mock、`safeInvoke` / `invoke` - 改了配置结构、版本文件、依赖或发布相关边界 - 需要判断“代码通过检查”是否已经等于“可以交付” ## Codex 工作流 ### 0. 路线图任务先校准目标 如果用户明确要求对齐路线图主线，先在脑内完成这三个判断，再决定跑什么校验： 1. 本轮改动对应路线图哪一节 2. 它推进的是主链，还是只是从属清理

What's inside
Steps it walks through
  1. Fast Path
  2. 何时使用
  3. Codex 工作流
  4. 0. 路线图任务先校准目标
  5. 1. 先判断改动类型
  6. 2. 先跑最贴边界的最低门槛
  7. 3. GUI 产品不要只看“代码通过”
  8. 4. 边界类改动必须成组检查
  9. 5. UI 改动必须补稳定回归
  10. 6. 本地入口与 CI 口径保持一致
  11. 7. 交付结论必须明确
  12. Codex 约束
  13. 输出要求
Commands it runs
npm run verify:local
npm run verify:local:full
More from lime
All skills →
personal-ip-knowledge-builder将访谈稿、聊天记录、简历、公开内容、业务资料、案例和既有 DOCX/Markdown 文档，提炼成可被 AI 长期调用的个人 IP 知识库。适用于用户要求“生成个人知识库”“整理成个人 IP…Otherlime-release-workflow准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送。Workflow & Productivitycontrol-browserResearch and inspect pages through Lime's managed browser session.Otherbrand-persona-knowledge-builder将品牌定位、价值观、受众画像、语气风格、内容样例、危机回应和表达禁区，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI…Content & Marketingbrand-product-knowledge-builder将品牌产品资料、规格参数、卖点证据、FAQ、价格权益、竞品区别和合规边界，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI…Content & Marketinglime-governanceGovern Lime legacy cleanup, fact-source convergence, current/compat/deprecated/dead classification…Other
About this skill
What does the lime-quality-workflow skill do?

Choose Lime validation commands for GUI, command/bridge, config, version, and PR-readiness changes.

How do I install it?

Run `npx skills add limecloud/lime --skill lime-quality-workflow --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.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.