github/deer-flow
1
0
Fork 0
mirror of https://github.com/bytedance/deer-flow.git synced 2026-08-01 19:06:01 +00:00
Code Issues Packages Projects Releases Wiki Activity
deer-flow/skills/public/skill-reviewer/references/report-rendering.md
Ryker_Feng 41658c5ff4
feat(skills): add skill review quality gate (#4037) 
* feat(skills): add skill review quality gate

* fix(skills): skip review eval fixtures in CI

* fix(skills): ignore review eval fixtures in bundled scans

* fix(skill-review): harden review gate boundaries

* fix(skills): address skill review gate feedback
2026-07-11 15:58:07 +08:00

1.3 KiB
Raw Permalink Blame History

Report Rendering

The canonical machine contract is review-report.v1. Markdown is a localized view of that report, not a second source of truth.

Full Review Sections

  1. Executive Summary
  2. Readiness
  3. Assurance
  4. Scope and Completeness
  5. Findings
  6. Dimension Review
  7. Trigger Analysis
  8. Resource and Script Review
  9. Evidence
  10. Suggested Rewrites
  11. Recommended Actions

Focused reviews may omit unrelated analytical sections, but must keep scope, readiness, assurance, evidence, and recommended actions.

Machine Enums

Do not translate enum values in structured output:

  • blocked
  • revise
  • publish_candidate
  • static_only
  • trigger_checked
  • behavior_verified
  • regression_verified
  • pass
  • concern
  • blocker
  • not_assessed

Localized labels may appear next to enums:

  • blocked: Not ready / 不可发布
  • revise: Needs revision / 需修订
  • publish_candidate: Publish candidate / 可作为发布候选
  • static_only: Static review only / 仅静态审查

Finding Format

Each issue should include:

  • severity: blocker, major, or minor;
  • confidence: high, medium, or low;
  • location: path and line when available;
  • observed evidence;
  • user impact;
  • remediation;
  • suggested replacement when there is a small paste-ready fix.

Avoid large quotes. Never quote suspected secrets.