Analyze git changes to classify modifications and assess impact and risk.
npx skills add https://github.com/ConaryLabs/Mira --skill diff-conarylabs
Please help me install this Agent Skill. Skill: diff Source: https://github.com/ConaryLabs/Mira/tree/main/plugin/skills/diff Command: npx skills add https://github.com/ConaryLabs/Mira --skill diff-conarylabs
This Skill helps developers quickly understand the semantic impact of code changes by automatically classifying changes, identifying affected areas, and highlighting risk.
Use the diff skill to analyze changes between two refs, for example: /mira:diff --from HEAD~1 --to HEAD The Skill will return a structured report with classifications, impacts, and risk.
High-intent search queries and answers about installing and using this skill.
To assess semantic impact before merging, analyze git changes to classify modified elements, identify downstream callers, and highlight potential ripple effects. This provides structured risk insights and impact classification for code reviews.
Semantic code change classification distinguishes new, modified, deleted, and refactored elements within git diffs. It works by running diffs between refs and producing structured output that evaluates impact and risk findings.
Yes, you can analyze code changes and risks across mixed-language repositories. The analysis applies to code reviews, pull request evaluations, and post-commit analyses to identify module dependencies and potential ripple effects.
To run a semantic diff analysis between two git refs, execute a diff command specifying the source and target refs like HEAD~1 and HEAD. The tool returns a structured report with classifications, impacts, and risk findings.
The best way to identify downstream callers and module dependencies is to perform an impact analysis on your git changes. This process highlights affected areas and potential ripple effects to evaluate risk before merging.
ThomasRohdeCompare two ECM model Git refs and summarize capability-model differences by category.
s3nex-comCoordinate pull request lifecycle from review through merge with mandatory gates.
ayeshakhalid192007-devAnalyze codebases for security, performance, and maintainability issues across files and dependencies.
lalulaliReview git diffs for correctness, security, performance, and pattern adherence.
