Analyze Git changes before submitting or merging a pull request. Assess risk and complexity, classify changes, suggest reviewer roles, and identify files needing closer inspection using diff statistics and file-level risk analysis.
Analyze git diffs for risk scoring, reviewer recommendations, and change classification. Use when preparing a PR, reviewing a large or cross-module change, or before merging to assess risk and pick reviewers.
Review the instructions the agent will receive before you install.
Analyze git diffs for risk, complexity, and reviewer assignment.
Before submitting a PR or after making significant changes, analyze the diff to understand risk level, get reviewer recommendations, and classify the type of change.
HEAD for uncommitted work, main..BRANCH for a branch (--branch), or the PR's base..head range (--pr, resolve it with gh pr view N --json baseRefName,headRefName). The analyze_* tools take a ref and run git themselves; they do not accept diff text.mcp__plugin_ruflo-core_ruflo__analyze_diff with { ref, includeFileRisks: true } for a comprehensive analysismcp__plugin_ruflo-core_ruflo__analyze_diff-risk with { ref } for a quantified risk assessmentmcp__plugin_ruflo-core_ruflo__analyze_diff-classify with { ref } to categorize (feature, bugfix, refactor, etc.)mcp__plugin_ruflo-core_ruflo__analyze_diff-reviewers with { ref, limit } for roles inferred from paths and risk; check CODEOWNERS separately when assigning peoplemcp__plugin_ruflo-core_ruflo__analyze_diff-stats with { ref } for line counts, file counts, complexity metricsmcp__plugin_ruflo-core_ruflo__analyze_file-risk with { path } (required) for each file the earlier steps flaggedNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.