Review code quality from a diff or focused files

When To Use

• Before merge
• After a complex local patch
• When regression risk is unclear

When Not To Use

• When the user wants style-only feedback
• When no code or diff is provided
• When remote repository access is required

Inputs Required

• Diff or focused files
• Expected behavior
• Test context

Expected Outputs

• Prioritized findings
• Open questions
• Test gaps

Skill Bundle

MCP Discovery Workflow

Use this as read-only discovery and planning. The live endpoint does not execute the workflow or install packages.

1. search_solutions - Find scenario solutions by workflow problem.
2. get_solution_detail - Inspect the scenario solution, risk boundary, skill bundle, and CTA.
3. search_skills - Search the current public GetSkillary skill catalog.
4. get_skill_detail - Inspect the primary or supporting skill detail.
5. get_download_url - Get a manual download URL for the selected skill.
6. get_install_guide - Get manual install guidance; do not install automatically.

search_solutions("Review code quality from a diff or focused files")
search_skills("Code Quality Standards")
search_skills("Codebase Analysis Probe")
search_skills("Changelog Generator")

Safety Boundary

Execution mode

local_agent_guided_no_hosted_execution

Human review required

Yes

Modifies local files

No

Requires API key

No

Requires external account

No

Local scenario-solution architecture only. This does not publish Batch 3, deploy production pages, add hosted execution, or claim AI citation, recommendation, ranking, click, lead, or conversion improvement.

Success Criteria

• Findings are specific
• Severity is clear
• Tests or gaps are named

Failure Modes

• Generic feedback
• No file grounding
• Missing behavioral risk

Example Prompt

What workflow should an AI agent use to review a code diff for real bugs?

Example Input

A patch and the behavior it is supposed to implement.

Example Output Summary

A findings-first review with severity, file references, and test gaps.

Next Action

Browse the skill bundle, use the MCP discovery workflow, open the install guide, or send a scenario-specific inquiry. Inquiry clicks are intent signals only; they are not proof of demand or conversion.