skills.rest
danielbaustin
danielbaustinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

repo-code-review

Identify high-risk areas across a repository with a findings-first code review.

4|1|Updated Feb 3, 2026
Search Tags:#security#risk-assessment#inventory#code-review#repository-analysis#build-config#repo-review
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-code-review-danielbaustin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-code-review
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/repo-code-review
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-code-review-danielbaustin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables teams to perform deterministic, repo-wide reviews that surface high-impact findings across code, tests, dependencies, and tooling, helping prevent regressions, security risks, and maintainability issues before they reach production.

Core Features & Use Cases

  • Finds bugs, regressions, security concerns, and maintainability risks across a whole repository or large slices.
  • Prioritizes risky surfaces (top-level manifests, dependency/build config, entrypoints, and critical code paths) and emits actionable findings with suggested fixes.
  • Supports repo-wide reviews, targeted path reviews, risk assessments, and release-readiness checks with a findings-first workflow.

Quick Start

Analyze a repository by requesting a findings-first repo review to generate a structured surface of risks and recommended actions.

Frequently Asked Questions about repo-code-review

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

FAQPage Schema
How do I perform a repo-wide code review to find security risks?▼

A repo-wide code review identifies high-risk areas by validating top-level manifests, dependencies, build configs, and critical code paths to generate deterministic findings and actionable surfaces. It prioritizes risky surfaces and emits suggested fixes.

What is the best way to assess release-readiness for a repository branch?▼

Assessing release-readiness involves analyzing branch diffs and targeted paths to surface regressions and maintainability risks. It validates toolchain configuration and entrypoints to produce a structured surface of risks with recommended actions.

Can I review specific file paths instead of a whole repository for risk assessment?▼

Yes, targeted path reviews evaluate specific file slices rather than the whole repository. This approach prioritizes critical code paths and emits actionable findings with suggested fixes to prevent regressions and maintainability issues.

Does a findings-first repository analysis work without external dependencies?▼

A findings-first repository analysis operates with no external dependencies. It directly inspects manifests, dependency configs, and entrypoints to produce deterministic findings and actionable risk surfaces.

When do I need a structured repository analysis for build config and dependencies?▼

A structured repository analysis is needed when validating top-level manifests, build configs, and dependencies to prevent security risks and regressions. It surfaces high-impact findings across tooling and code paths before production release.

What are the limitations of automated code review for repository risk assessment?▼

Automated code review limitations involve focusing on deterministic findings from manifests, dependencies, and critical paths. It prioritizes actionable surfaces but requires manual implementation of the suggested fixes to resolve identified risks.

Related Skills

Explore More Software Engineering Skills→
reedomreedom

collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

Community
Advanced
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
brenordvbrenordv

security

Audit software systems for security vulnerabilities and regulatory compliance.

Community
Advanced
vrcmsvrcms
1

verification-loop

Execute build, type, lint, test, and security checks in a verification pipeline.

Community
Advanced