be-lead

Analyze backend code changes for high-severity bugs and security issues.

1|Updated Mar 24, 2026

Search Tags:#architecture #performance #security #openapi #backend #code-review #pull-request

Ready to run

npx skills add https://github.com/gridi-ai/gridi-skills --skill be-lead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: be-lead
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/be-lead
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill be-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes backend code changes to surface only high-severity issues such as bugs, security vulnerabilities, performance problems, and architecture violations, enabling focused reviews.

Core Features & Use Cases

Highlights critical defects and potential security issues across PR diffs
Checks for architectural or design inconsistencies and performance concerns in changed code
Suitable for BE reviews, API reviews, or PR reviews to improve quality with high-signal feedback

Quick Start

Provide a GitHub PR URL or path to review, and the skill will generate a focused high-severity report.

Frequently Asked Questions about be-lead

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

FAQPage Schema

How do I find high-severity bugs and security vulnerabilities in a pull request?▼

Backend code review analyzes PR diffs, file paths, or commit ranges to surface high-severity issues like bugs, security vulnerabilities, performance problems, and architecture violations. It requires repository context such as structure, tests, and migrations to generate actionable feedback.

What is high-signal backend code review and how does it work?▼

High-signal backend code review analyzes backend code changes to surface only high-severity issues like bugs, security vulnerabilities, performance problems, and architecture violations. It works with PR diffs, file paths, or commit ranges to provide structured, actionable feedback.

Can I review backend API code changes using a GitHub PR URL?▼

Yes, you can review backend API code changes using a GitHub PR URL. Provide the URL or file path, and the review process will analyze the PR diff to generate a focused report highlighting critical defects, security issues, and architectural inconsistencies.

Does backend code review require repository structure and test context?▼

Yes, backend code review requires repository context such as structure, tests, and migrations. This contextual information is necessary to accurately analyze code changes and identify high-severity issues, security vulnerabilities, and architecture violations.

What is the best way to check for architecture violations in backend code?▼

The best way to check for architecture violations in backend code is to analyze PR diffs or commit ranges against repository context. This surfaces architectural or design inconsistencies alongside performance concerns and security vulnerabilities, providing focused high-signal feedback.

Why does my backend code review miss critical security issues?▼

Backend code reviews may miss critical security issues if they lack sufficient repository context like structure, tests, and migrations. Providing complete PR diffs and file paths ensures the analysis surfaces high-severity vulnerabilities and performance problems effectively.