From majestic-engineer
Automates code review of changed files using RepoPrompt MCP review mode, parsing for APPROVED verdict and returning structured approved/rejected result for relay workflows.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerThis skill uses the workspace's default tool permissions.
**Audience:** Developers using the relay workflow who need automated code review via RepoPrompt.
Performs code reviews with semantic diffs via difft/delta, routes to experts for TypeScript/React/Python/Go/Rust/Vue/SQL, auto-creates tasks for critical issues on staged changes, files, or PRs.
Performs immediate code review on Git diffs at task/PR completion, matching against TASKS.md context, running hook gates, spec compliance, security checks, and optional AI multi-review.
Dispatches code reviewer subagent to evaluate git changes between SHAs after tasks, major features, or before merging. Integrates with subagent-driven development to catch issues early.
Share bugs, ideas, or general feedback.
Audience: Developers using the relay workflow who need automated code review via RepoPrompt.
Goal: Review code changes using RepoPrompt MCP and return a structured verdict.
task_id: string # Task identifier (T1, T2, etc.)
changed_files: string[] # List of changed file paths
{
"verdict": "approved" | "rejected",
"reason": "string"
}
Ensure RepoPrompt is on the correct workspace for the project:
Call repoprompt/manage_workspaces with:
{
"action": "switch",
"workspace": "<project-name>"
}
Use repoprompt/chat_send MCP tool with review mode:
{
"new_chat": true,
"mode": "review",
"selected_paths": ["<changed-files>"],
"message": "Review code changes for task <task_id>. Check for bugs, security issues, code quality. If acceptable, respond APPROVED. Otherwise list issues.",
"chat_name": "relay-review-<task_id>"
}
Key: mode: "review" includes git diffs automatically via gitInclusion.
| Response Pattern | Verdict |
|---|---|
| Contains "NOT APPROVED" or "DISAPPROVED" | rejected |
| Contains "APPROVED" (without negation) | approved |
| No clear verdict | rejected |
{
"verdict": "approved",
"reason": "Code review passed - no issues found"
}
Or on rejection:
{
"verdict": "rejected",
"reason": "Security vulnerability found in auth.rb:45"
}
| Scenario | Action |
|---|---|
| RepoPrompt MCP not available | Return { "verdict": "approved", "reason": "RepoPrompt unavailable" } |
| Workspace switch fails | Return { "verdict": "approved", "reason": "Could not switch workspace" } |
| chat_send fails | Return { "verdict": "approved", "reason": "Review failed - auto-approved" } |
Design principle: Fail-open to avoid blocking relay workflow.