librefang-registry/workflows/code-review.toml

id = "code-review"
name = "Code Review"
description = "Parallel code analysis pipeline that evaluates correctness, security, and style independently, then synthesises findings into a unified review summary."
category = "engineering"
tags = ["code", "review", "security", "quality"]

[i18n.zh]
name = "代码审查"
description = "并行代码分析流水线，独立评估正确性、安全性和代码风格，然后将发现汇总为统一的审查报告。"

[[parameters]]
name = "code"
description = "The source code or diff to review"
param_type = "string"
required = true

[[parameters]]
name = "language"
description = "Programming language of the code"
param_type = "string"
required = false
default = "auto-detect"

[[parameters]]
name = "context"
description = "Additional context about the codebase or change purpose"
param_type = "string"
required = false
default = ""

[[steps]]
name = "review_correctness"
prompt_template = """
Review the following {{language}} code for correctness. Analyse:
- Logic errors and edge cases
- Error handling completeness
- Null/undefined safety
- Off-by-one errors and boundary conditions
- Resource leaks (memory, file handles, connections)
- Concurrency issues (race conditions, deadlocks)

Context: {{context}}

Code:
{{code}}
"""

[[steps]]
name = "review_security"
prompt_template = """
Perform a security review of the following {{language}} code. Check for:
- Injection vulnerabilities (SQL, command, XSS)
- Authentication and authorisation flaws
- Sensitive data exposure (logging secrets, hardcoded credentials)
- Input validation gaps
- Insecure cryptographic usage
- Path traversal and SSRF risks
- Dependency vulnerabilities

Context: {{context}}

Code:
{{code}}
"""

[[steps]]
name = "review_style"
prompt_template = """
Review the following {{language}} code for style and maintainability. Evaluate:
- Naming conventions and clarity
- Function/method length and complexity
- Code duplication
- Documentation and comments quality
- Consistent formatting
- Appropriate use of language idioms
- API design and public interface clarity

Context: {{context}}

Code:
{{code}}
"""

[[steps]]
name = "synthesise"
prompt_template = """
Synthesise the three independent code review analyses below into a unified review summary. Prioritise findings by severity (critical, high, medium, low). Remove duplicates across analyses. Produce a final verdict: approve, request-changes, or needs-discussion.

Correctness review:
{{review_correctness}}

Security review:
{{review_security}}

Style review:
{{review_style}}
"""
depends_on = ["review_correctness", "review_security", "review_style"]

[i18n.zh-TW]
name = "程式碼審查"
description = "並行程式碼分析流水線，獨立評估正確性、安全性與程式碼風格，再將發現彙整為統一的審查報告。"

[i18n.ja]
name = "コードレビュー"
description = "並列コード解析パイプライン。正確性・セキュリティ・スタイルを独立評価し、統合レビューサマリに集約。"

[i18n.ko]
name = "코드 리뷰"
description = "병렬 코드 분석 파이프라인. 정확성·보안·스타일을 독립 평가한 뒤, 통합된 리뷰 요약으로 정리합니다."

[i18n.de]
name = "Code-Review"
description = "Parallele Code-Analyse-Pipeline: bewertet Korrektheit, Sicherheit und Stil unabhängig und fasst die Ergebnisse in einer einheitlichen Review-Zusammenfassung zusammen."

[i18n.es]
name = "Revisión de código"
description = "Pipeline paralelo de análisis que evalúa corrección, seguridad y estilo de forma independiente y sintetiza los hallazgos en un informe unificado."

[i18n.fr]
name = "Revue de code"
description = "Pipeline d'analyse parallèle qui évalue indépendamment la justesse, la sécurité et le style, puis synthétise les résultats dans un rapport unifié."