Project Coding Standards

Testing

• Write tests before code (TDD)
• For bugs: write a failing test first, then fix (Prove-It pattern)
• Test hierarchy: unit > integration > e2e (use the lowest level that captures the behavior)
• Run npm test after every change

Code Quality

• Review across five axes: correctness, readability, architecture, security, performance
• Every PR must pass: lint, type check, tests, build
• No secrets in code or version control

Implementation

• Build in small, verifiable increments
• Each increment: implement → test → verify → commit
• Never mix formatting changes with behavior changes

Boundaries

• Always: Run tests before commits, validate user input
• Ask first: Database schema changes, new dependencies
• Never: Commit secrets, remove failing tests, skip verification

这份文件与技能体系一一对应："five axes" 评审标准来自 [skills/code-review-and-quality/SKILL.md](https://gitcode.com/GitHub_Trending/agentskill/agent-skills/blob/469d00f4e67ff4a21eb6e6e467a086c9a1f1deb8/skills/code-review-and-quality/SKILL.md?utm_source=gitcode_repo_files) 的五维评审框架；"Prove-It pattern"（先写失败测试再修 bug）来自 [skills/test-driven-development/SKILL.md](https://gitcode.com/GitHub_Trending/agentskill/agent-skills/blob/469d00f4e67ff4a21eb6e6e467a086c9a1f1deb8/skills/test-driven-development/SKILL.md?utm_source=gitcode_repo_files) 的"测试即证据"原则；"小步增量、implement → test → verify → commit" 则是 [skills/incremental-implementation/SKILL.md](https://gitcode.com/GitHub_Trending/agentskill/agent-skills/blob/469d00f4e67ff4a21eb6e6e467a086c9a1f1deb8/skills/incremental-implementation/SKILL.md?utm_source=gitcode_repo_files) 的核心循环。项目指令负责"常驻约束"，斜杠命令负责"按需触发"，两者互补。

此外，文档建议在 Copilot Chat 中配合专门的 agent 人格做定向评审（即上文 `@code-reviewer` 等用法），形成"项目指令兜底 + 人格按需深审"的双层质量闸口。

## 生命周期工作流：六个阶段全部以技能名调用

技能默认即用户可调用，因此只要被发现，整个开发生命周期无需额外配置即可用技能本名触发：

| 阶段 | Copilot 调用方式 | 说明 |
|------|------------------|------|
| Define | `/spec-driven-development` | 写代码前先产出结构化 spec |
| Plan | `/planning-and-task-breakdown` | 产出 `tasks/plan.md` 与 `tasks/todo.md` |
| Build | `/incremental-implementation` | 与 `/test-driven-development` 搭配；一次只做一个切片 |
| Verify | `/test-driven-development` | 红-绿-重构；bug 用 Prove-It 模式 |
| Review | `/code-review-and-quality` | 五轴评审 |
| Ship | `/shipping-and-launch` | 上线就绪检查 |

在 Copilot 聊天框输入 `/` 即可浏览当前工作区实际加载了哪些命令。

斜杠命令不可见时的兜底是**自然语言**，它在任何 Copilot 界面都可用，无论斜杠命令是否显示：

> Use the spec-driven-development skill to write a spec for [the feature].

> Use the code-review-and-quality skill to review my staged changes.

### 可选：自建 `/spec` 风格短别名

VS Code 的 extension-host 本地 agent 支持放在 `.github/prompts/<name>.prompt.md` 的提示词文件（prompt files），每个文件对应一个 `/<name>` 斜杠命令。**但要注意：Agent Host 不使用 prompt 文件**——如果你运行在 Agent Host 上，请直接用技能全名。

先明确别名的定位：别名只是到某个技能的"薄快捷方式"，仅此而已。它们**不复现**本仓库 Claude Code 命令里的编排逻辑——例如 `/build auto` 的"单次批准后连续实施全部任务"、`/ship` 的"多人格并行扇出"。在 Copilot 上复刻那些编排是另一项独立工作，不是一个单文件别名能覆盖的。因此默认优先用技能名，只有当短形式确实值得多维护一个文件时才建别名。

官方给出的 `/spec` 别名创建示例（`[ -e ... ] ||` 保护避免覆盖已有文件）：

```bash
mkdir -p .github/prompts
[ -e .github/prompts/spec.prompt.md ] || cat > .github/prompts/spec.prompt.md <<'EOF'
---
description: Write a structured spec before writing code
---

Use the spec-driven-development skill.

Ask clarifying questions about the objective and target users, core features and
acceptance criteria, stack preferences and constraints, and known boundaries.
Then write a spec covering objective, commands, project structure, code style,
testing strategy, and boundaries. Save it as SPEC.md in the project root and
confirm with me before any code is written.
EOF