cmd-workflow-diff-review

Multi-perspective code review analyzes pull request diffs across security, quality, and testing lenses. It structures the analysis through Context, High-Level, Line-by-Line, and Summary phases to identify bugs, security risks, and maintainability issues before merging.

Checking a local git diff for security risks involves reading the local git state and applying a structured review protocol. This process evaluates code quality, security vulnerabilities, and testing gaps to deliver a structured findings report and a go/no-go decision guide.

Yes, automated diff review works with language-specific patterns by analyzing context, scope, and language-specific gotchas. It evaluates whether your code changes align with existing project conventions and patterns before you open a pull request.

Yes, you can get a structured go/no-go decision guide directly from your branch diff. The review workflow reads local git state, identifies performance concerns and maintainability issues, and outputs a clear decision guide for merging.

To review your branch against main before opening a PR, run a pre-submission diff review. This evaluates your current changes across multiple perspectives to ensure they align with project conventions and catch bugs before submission.

The structured PR diff analysis workflow relies on reading local git state and the structured protocol in SKILL.md. Limitations include its dependency on local repository availability and the need to manually interpret the generated findings report for complex architectural decisions.