Menu
Nhac update living docs sau moi PR/wave
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Dùng khi user nói 'start new session', 'bắt đầu session mới', '/start-session', 'what's the state?', 'tình trạng hiện tại', hoặc khi cần load context sau khi /clear. Load: CLAUDE.md digest, current wave, open PRs, failing CI, active blockers. Output: single summary block. Cũng check session-lock conflicts khi chạy parallel agents.
Dùng khi user nói 'plan wave', 'cluster gaps', 'wave-pack', 'next wave', hoặc khi cần group ≥3 disjoint gaps thành 1 wave-pack chạy parallel agents. Output: wave plan markdown (foundation PR-ready) + file-overlap matrix + 3-5 agent prompts. Codify pattern từ Wave Observability 2026-04-28 (3 gaps trong ~75 min vs ~6h serial = 5x speedup).
Use when PR touches kitehub-email templates (*.html under templates/emails/), kiteclass-gateway email templates, any new customer-facing email, phrases 'review email', 'kiểm tra email template', 'gửi email cho tenant', 'trial-expiry email', 'welcome email'. Enforces brand/legal/i18n/mobile/GDPR-PDPL gate before customer send per output-review-mandate §5.7.
Dùng khi 'kit parity', 'kit production parity', 'review Track 2 port', 'port theo ui kit', 'kit vs production', 'back-port kit', hoặc trước khi merge PR port kit → production / production → kit. Verifies 4-layer V-model parity (要件定義 / 基本設計 / 詳細設計 / コンポーネント設計) giữa HTML kit prototype và production Next.js code. Bidirectional: kit→production port AND production→kit back-port (production led). Output report /4-layer to documents/04-quality/audits/parity/.
Dùng khi PR thay đổi AI Branding behavior — model swap (Ollama → Bedrock, Llama → Gemma), prompt template change, AIClient/Step interface, ContentModerationService, InstanceQualityReviewer logic, 5 *QualityCheck classes. Auto-trigger qua audit-gate khi files match `kiteclass/kiteclass-core/src/main/java/com/kiteclass/core/module/{ai,branding,instance,quality,moderation,provisioning}/**/*.java`. Manual checklist mode (5 sections × scoring) + delta-vs-baseline rubric. Output: `documents/04-quality/audits/ai-branding/YYYY-MM-DD-<change>.md`.
Dùng khi user nói 'security audit', 'pentest', 'kiểm tra bảo mật', 'dependency scan', hoặc trước production deploy. Deep security check /100 — vượt xa quality-audit §2. v2 audit format mandatory per GAP-564: mỗi control bind với evidence block (Command run + Output + Verdict + Evidence artifact ID).
| name | docs-freshness |
| description | Nhac update living docs sau moi PR/wave |
| user-invocable | false |
| Doc | Update khi | Check |
|---|---|---|
README.md (root) | Them/xoa folder, thay doi tech stack, them service | Folder structure khop reality |
CLAUDE.md | Thay doi quy trinh, them skill, doi convention | Context du cho session moi |
documents/01-business/*.md | Thay doi business logic, config, email trigger | Rules khop code |
documents/01-business/README.md | Them/xoa business doc | Index day du |
documents/03-planning/quality/*.md | Sau moi quality audit | Score phan anh thuc te |
.claude/skills/_README-skills-index.md | Them/xoa/rename skill | Index khop files |
git diff cua wave voi living docs list01-business/X.md khong update → flag/wave-completion-check Level 5 goi docs-freshness check/quality-audit Category 8 dung docs-freshness criteriaaudit-to-gap-pipeline.md Step 2.5 state-check if you need the harder "code-doc divergence" checkREADME.md is living, but service-level READMEs are NOT in this list — only the 6 docs in §Living Docs are tracked; Wave Meta-Gov 1 introduced scripts/check-readme-freshness.sh (CI job readme-freshness, GAP-255) for the broader 46-README freshness window — they are complementary, not duplicatesquality/business-logic-audit/SKILL.md for value-level verification.husky/ only fires on staged files; if a PR re-bases or rewrites history, drift between branches won't trigger a warning. Re-run check on the PR base SHA, not just HEADdocuments/01-business/*/rules.md 3-layer rule trumps this list — when a domain folder has the 3-file structure (rules.md / use-cases.md / api-contract.md), all three are living together; do not flag only rules.md as drift while leaving the matching api-contract.md stale (CLAUDE.md §Business Logic Documents)