skills.rest
Endor-Solutions-Architecture
Endor-Solutions-ArchitectureOFFICIAL
Explore all skills by this author →
GitHub

endor-review

Analyze Git changes for security risks before merging pull requests.

2|Updated Feb 4, 2026
Search Tags:#dependencies#license#secrets#PR#SAST#security-review
One-click install
npx skills add https://github.com/Endor-Solutions-Architecture/endor-solutions-claude-skills --skill endor-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: endor-review
Source: https://github.com/Endor-Solutions-Architecture/endor-solutions-claude-skills/tree/main/.claude/skills/endor-review
Command: npx skills add https://github.com/Endor-Solutions-Architecture/endor-solutions-claude-skills --skill endor-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the current git diff or branch for security issues before creating a PR. Performs dependency checks, SAST analysis, secrets detection, and license compliance review to gate merges.

Core Features & Use Cases

  • Dependency checks during PRs to catch vulnerable or outdated libraries.
  • SAST analysis and secrets detection for modified code paths.
  • License compliance review to ensure legal usage and risk mitigation.
  • Use Case: When preparing a PR, run a pre-PR security review to surface new risks and require remediation before merge.

Quick Start

Trigger the pre-PR security review on your branch using the endor-review workflow. Ensure the MCP server is configured and authenticated, then use the /endor-review trigger or the corresponding UI command in Claude Code to run the scan.

Frequently Asked Questions about endor-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security review before merging a pull request?▼

A pre-PR security review analyzes your git diff to surface risks like vulnerable dependencies, secrets, and SAST findings before merging a pull request. It enforces a pre-merge gate to require remediation of new issues detected in modified code and configuration.

What does SAST analysis check for during a PR workflow?▼

SAST analysis during a PR checks modified source code paths for security vulnerabilities. It runs alongside secrets detection and dependency checks on the current git branch to identify risks before code is merged.

Can I check license compliance for new dependencies in a git diff?▼

License compliance review checks new dependencies introduced in your git diff to ensure legal usage and mitigate risk. It is part of the pre-PR security review that gates merges until compliance is verified.

Do I need an MCP server configured to scan for secrets in modified code?▼

You need the Endor MCP server configured and authenticated to scan for secrets in modified code. The pre-PR security review integrates with this tooling to gather findings and enforce the merge gate.

Are incremental scans supported for detecting security risks in pull requests?▼

Incremental scans are supported to detect security risks in pull requests by analyzing only the current git changes. This surfaces new risks in dependencies, source code, and configuration efficiently before merge.

Related Skills

Explore More Software Engineering Skills→
endorlabsendorlabs
2

endor-scan-full

Build a call graph to identify exploitable vulnerabilities in code.

Official
Advanced
ZiadNagarZiadNagar

security-audit

Identify and remediate security vulnerabilities in web application and API codebases.

Community
Advanced
MacPhobosMacPhobos

Security Scanning

Automate security scanning of code and dependencies for vulnerabilities.

Community
Intermediate
froggugugugufroggugugugu

security-scan

Execute SCA, SAST, DAST, and secret detection scans to report vulnerabilities.

Community
Advanced