truth-layer
以徹底誠實驗證聲明
開發團隊經常面臨誤報問題和在部署時才浮現的未被發現的阻礙。此技能會根據實際程式碼庫狀態驗證所有聲明,並在問題真正解決之前阻止進度。
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "truth-layer". Verify that the build completes successfully with no hidden errors or warnings
Resultado esperado:
BLOCKER FOUND: Turbopack build fails
- What failed: Cannot write manifest.json file
- Impact: Deployment cannot proceed
- Root cause: Missing directory structure in build output
- Current state: Build command exits with 0 but manifest not generated
- Next step: Create output directory structure before build
STOP PROGRESS on UI changes, API updates, feature deployment
Route to: Build Diagnostics Agent
A utilizar "truth-layer". Check if test coverage report is backed by actual test cases
Resultado esperado:
Truth Layer Verification: 2026-01-21T10:30:00Z
CLAIM: 100% test coverage on authentication module
REALITY: Test file is 412 bytes with empty describe blocks
CONFIDENCE: 95%
BLOCKERS FOUND: Yes
- Test file contains no assertions
- Coverage is false positive from stub file
DEPENDENT FEATURES BLOCKED: Authentication deployment, user management
ACTION: Write real test cases with assertions before claiming coverage
Auditoria de Segurança
SeguroThe skill is documentation-only with no executable code. All static findings are false positives from pattern detection in the JSON report itself and example code snippets within the documentation. The skill describes verification workflows but does not implement any network calls, filesystem operations, or command execution.
Pontuação de qualidade
O Que Você Pode Construir
防止錯誤的建置成功報告
透過執行實際建置命令並檢查日誌中的隱藏錯誤來驗證建置過程真正成功,而不是僅信任狀態碼。
驗證測試覆蓋率聲明
在接受覆蓋率報告前,透過分析檔案大小和解析測試結構來檢查測試檔案是否包含真實的測試案例而非空白存根。
以未解決的問題阻止部署
當存在型別錯誤、測試失敗或未解決的相依性時停止功能部署,即使建置看起來成功。
Tente Estes Prompts
Verify that the build completes successfully with no hidden errors or warnings
Check if test coverage report is backed by actual test cases and not empty stub files
Identify all blockers preventing deployment and list dependent features that cannot proceed
Validate that the user authentication feature works end-to-end including database, API, and UI layers
Melhores Práticas
- 執行實際的建置和測試命令而非檢查快取狀態,以確保當前狀態的準確性
- 根據使用的驗證方法設定信心閾值,手動檢查比自動化檢查具有更高的信心
- 在偵測到問題時立即建立阻礙報告,而不是等待任務完成
Evitar
- 僅從退出碼假設建置成功,而不檢查日誌中的隱藏錯誤或警告
- 在未驗證測試檔案包含真實斷言和邏輯的情況下接受測試覆蓋率百分比
- 在對所有相依系統執行端對端驗證前就報告功能已完成