Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
中文简介正在准备中。当前显示原文说明。
ash1794/vibe-engineering1642026年10月8日 更新
免费在 GitHub 公开
vibe-doc-quality-gate
Performs a fast 6-point quality check for technical documents (specs, design docs, READMEs). Use after editing any specification or design document.
中文简介正在准备中。当前显示原文说明。
查看安装方法包含的文件（1）
- SKILL.md2.6 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
vibe-doc-quality-gate
A fast quality gate for technical documents. Not a deep review — just catches the obvious structural issues.
When to Use This Skill
- After creating or editing a specification document
- After writing a design doc or technical RFC
- Before sharing a document for review
- Periodic document health checks
When NOT to Use This Skill
- For code review (use
vibe-quality-looporvibe-devil-advocate-review) - For informal notes or scratch documents
- For README files that are just getting started
The 6 Checks
1. Overview/Quick Start
Does the document have an overview or quick-start section that explains what this is and why it matters in <5 paragraphs?
- PASS: Overview exists with purpose and scope
- FAIL: No overview, or jumps straight into details
2. Structural Completeness
Does the document reference concrete artifacts?
- At least 3 file paths or API endpoints
- At least 1 data structure or type definition
- At least 1 error case or failure mode
- At least 3 test cases or validation steps
- PASS: All present | WARN: 2-3 present | FAIL: 0-1 present
3. Cross-Reference Integrity
Are references to other documents, APIs, or code valid?
- Check that referenced files exist
- Check that referenced types/functions exist
- PASS: All references valid | FAIL: Broken references found
4. Test Coverage
Does the document specify how to verify the implementation?
- At least 3 test cases for small docs
- At least 10 for large docs
- PASS: Adequate test coverage | WARN: Below threshold
5. Command Accuracy
Are commands, paths, and code snippets accurate?
- Do file paths exist (or are marked "to be created")?
- Do commands actually run?
- PASS: All verified | FAIL: Broken commands/paths
6. Self-Sufficiency
Could someone implement this without asking questions?
- Pick 3 random sections. Could you implement each without external context?
- PASS: Yes | FAIL: Ambiguous or incomplete sections
Output Format
Document Quality Gate: [Document Name]
Overall: PASS / WARN / FAIL
| Check | Status | Notes |
|---|---|---|
| 1. Overview | ✓/✗ | [notes] |
| 2. Structure | ✓/◐/✗ | [X/4 artifacts] |
| 3. Cross-refs | ✓/✗ | [X broken] |
| 4. Tests | ✓/◐ | [X cases] |
| 5. Commands | ✓/✗ | [X broken] |
| 6. Self-sufficiency | ✓/✗ | [notes] |
Issues to Fix
- [Specific issue with location]
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
中文简介正在准备中。当前显示原文说明。
ash1794/vibe-engineering1642026年10月8日 更新
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
中文简介正在准备中。当前显示原文说明。
ash1794/vibe-engineering1642026年10月8日 更新
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
中文简介正在准备中。当前显示原文说明。
ash1794/vibe-engineering1642026年10月8日 更新
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
中文简介正在准备中。当前显示原文说明。
ash1794/vibe-engineering1642026年10月8日 更新
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
中文简介正在准备中。当前显示原文说明。
ash1794/vibe-engineering1642026年10月8日 更新