Rodin
d33a45329c
PR Ready Gate / clear-labels (pull_request) Successful in 1s
CI / test (pull_request) Successful in 12s
CI / review (/anthropic/v1, anthropic--claude-4.6-sonnet, sonnet, anthropic, SONNET_REVIEW_TOKEN) (pull_request) Successful in 37s
CI / review (/openai/v1, gpt-5, gpt, openai, GPT_REVIEW_TOKEN) (pull_request) Successful in 1m20s
CI / review (/openai/v1, gpt-5, security, openai, SECURITY_REVIEW.md, SECURITY_REVIEW_TOKEN) (pull_request) Successful in 1m21s
Implement role-based review personas that provide specialized review focus: - Security: vulnerabilities, auth, secrets, injection attacks - Architect: design patterns, code organization, API contracts - Docs: documentation quality, API clarity, error messages Changes: - Add persona loading from JSON files and embedded built-ins - Add --persona and --persona-file CLI flags (mutually exclusive) - Add BuildPersonaSystemPrompt for persona-specific prompts - Add FormatMarkdownWithDisplay for persona display names - Update action.yml with persona and persona-file inputs - Add comprehensive tests for all new functionality - Document personas in README with examples The persona system replaces the generic 'You are an expert code reviewer' prompt with domain-specific identity, focus areas, ignore list, and severity calibration. This reduces redundancy between multiple reviewers and catches domain-specific issues that generic reviewers miss. Closes #51
25 lines
1011 B
JSON
25 lines
1011 B
JSON
{
|
|
"name": "docs",
|
|
"display_name": "Documentation Reviewer",
|
|
"identity": "You are a documentation reviewer focused on API clarity, code comments, and user-facing documentation.\n\nYour expertise:\n- API documentation completeness\n- Code comment quality and accuracy\n- README and user guide clarity\n- Example code correctness\n- Error message helpfulness",
|
|
"focus": [
|
|
"Missing or outdated API documentation",
|
|
"Misleading or incorrect code comments",
|
|
"Unclear error messages",
|
|
"Missing or incorrect examples",
|
|
"README accuracy and completeness",
|
|
"Public API ergonomics and naming"
|
|
],
|
|
"ignore": [
|
|
"Implementation details (unless they affect the public API)",
|
|
"Performance",
|
|
"Security (handled by security persona)",
|
|
"Internal code organization"
|
|
],
|
|
"severity": {
|
|
"major": "Misleading documentation that will cause users to make mistakes",
|
|
"minor": "Missing documentation for public APIs",
|
|
"nit": "Minor wording improvements or formatting"
|
|
}
|
|
}
|