菜单
Verify all production proof source links in pattern documents. Run automated checks for HTTP status, format, SHA permanence, and line-range content accuracy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a developer wants to apply a low-level, systems, or concurrency design pattern in their own code, drawing on the Battle-Tested Patterns catalog of 46 production-proven patterns. Triggers three ways: they name a pattern (ring buffer, circuit breaker, actor model, LRU cache, rate limiter, trie, bloom filter, WAL, semaphore, ...); they describe a problem one solves without naming it (fixed-size buffer that overwrites the oldest entry, cascading failures across services, throttling requests, deduplicating identical strings, ordering events without wall-clock time, snapshot isolation, prefix search, set membership without storing every key, ...); or they ask which pattern fits a problem or how two related patterns differ.
Use when reviewing or auditing an existing codebase against production-proven implementation patterns — checking whether the patterns it already implements (actor model, rate limiter, circuit breaker, LRU cache, write-ahead log, semaphore, ...) actually honor the canonical invariants, whether any are mislabeled (a "semaphore" that is really a mutex; an "MVCC" that keeps one version), whether any diverge from the reference, and which catalog patterns are absent. Triggers on "audit our architecture against best practices", "do we implement X correctly", "are our patterns right", "pattern conformance", "is this really a <pattern>?". This grades patterns already present; its companion adopt-pattern adds new ones.
Structured debugging loop for exercise tests or build failures. Reproduce → isolate → hypothesize → fix → verify.
Guided workflow to create a new pattern following the project template and quality standards. Walks through topic validation, source verification, implementation, exercises, challenge questions, and bilingual docs.
| name | verify-source |
| description | Verify all production proof source links in pattern documents. Run automated checks for HTTP status, format, SHA permanence, and line-range content accuracy. |
You are verifying production proof links in this repository. This is the most critical quality check — every pattern's credibility depends on accurate, live source links.
pnpm verify-links
This scans all docs/**/*.md and root README.md/README.zh-CN.md files, extracts GitHub URLs, and checks:
#L18-L22)#L1 file-level links exist in Production ProofOutput categories:
✅ [proof] — valid Production Proof link with line numbers✅ [other] — valid non-Production-Proof link⚠️ [proof] — Production Proof link missing line numbersℹ️ — branch-based link (not SHA permalink)❌ — broken link (HTTP error)For CI mode (exit 1 on broken links): pnpm verify-links -- --ci
If the report shows branch-based links, convert them:
tsx scripts/convert-to-sha-links.ts --dry-run # preview changes
tsx scripts/convert-to-sha-links.ts # execute conversion
Authentication: prefers gh auth token (system keyring), falls back to GITHUB_TOKEN env var.
For links that pass HTTP checks, verify that the referenced code lines actually match the pattern:
pnpm verify-lines # Check all Production Proof links
pnpm verify-lines --pattern <name> # Check a single pattern
pnpm verify-lines --verbose # Show all results including passes
pnpm verify-lines --section all # Also check "More Production Uses" section
pnpm verify-lines --no-cache # Re-fetch everything (ignore cache)
This script performs two layers of verification:
Output:
✅ — line range valid and keywords found⚠️ — line range valid but no keywords found (review manually)❌ FAIL — line range exceeds file length (must fix)❌ ERROR — fetch failed (network issue, retry)Results are cached in tmp/line-range-cache.json (SHA links are immutable, so cache is permanent).
For any ⚠️ warnings from verify-lines, manually confirm:
For ❌ FAIL results (line range out of bounds), the link must be fixed:
Output a summary:
For broken links, suggest the fix per .sop/06-broken-link-fix.md.
<!-- TODO --> markerpnpm verify-links, pnpm verify-lines), then manually for warnings