wondelai/skills✦ 精选0°

improve-code-quality

仓库创建 2026年1月29日最近提交 4 天前SkillHot 收录 1 小时前
▸ 精选理由

系统化提升代码质量并生成文档,利于团队交接与运维。

▸ 风险提示

会修改或写入项目文件,使用前请备份并审查变更。

这个 Skill 做什么

将原型代码改造成可发布、可测试且可维护的高质量产品。

把能跑通但没测试、结构混乱的原型,变成可发布、可测试、好维护的产品:补测试、梳理边界、重构并生成项目文档(如 TESTING.md、TECH-DEBT.md 等)。当你想把 AI 生成或草稿级项目“硬化”上线、逐步提升代码质量时用。过程是交互式、分阶段的,会把决策记录到 docs/ 里,方便随时中断和继续。

▸ 展开 SKILL.md 英文原文

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, RELIABILITY.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For a large aged codebase, use remove-technical-debt; to decide structure before building, use design-code-architecture; for a product and UX pass, use improve-app. For one framework in isolation, invoke that skill di

开发编程代码质量测试覆盖重构通用
1.7k
Stars
178
Forks
40
仓库内 Skill
+178
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/wondelai/skills/main/improve-code-quality/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/wondelai/skills/main/improve-code-quality/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Improve Code Quality

Turn a working-but-untested vibe-coded prototype into a product you can ship and operate. This is an
interactive, resumable journey of nine phases: the agent asks before every decision and records the
outcome in your project's `docs/` folder, so you can stop after any phase and pick up later. A
week-old prototype is already legacy code — so the first move is a safety net, and every phase after
it is verifiable because of that net.

## Core Principle

**A week-old untested prototype is already legacy code: flip tactical to strategic — safety net
first, then readability, structure, and production hardening in order.** This skill sequences the
phases, asks the decision q
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有