admin.code_review_graph

Execute admin-controlled code-review graph operations on allowlisted repositories.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill admin-code-review-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admin.code_review_graph
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/skills/admin.code_review_graph
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill admin-code-review-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Admins often need to perform Code Review Graph operations (build, impact radius, and review context) in a controlled environment, balancing visibility with safety. This Skill provides guardrails and an allowlisted repository scope to prevent accidental changes or data leaks.

Core Features & Use Cases

  • Guarded admin CRG operations with repo allowlists, timeouts, and sanitized outputs
  • Supports build, impact radius, and review context queries
  • Validates inputs such as target_file for impact/context and enforces safe execution boundaries
  • Provides auditable, concise results including status, summary, repository, duration, and Ref for traceability

Quick Start

Ask the admin to run a CRG operation (build, impact, or context) on an allowlisted repository.

Frequently Asked Questions about admin.code_review_graph

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

FAQPage Schema
How do I calculate the impact radius of code changes across multiple repositories?

To calculate impact radius across repositories, this Skill executes admin-controlled queries on an allowlisted repository set. It validates required inputs like target_file and returns sanitized, auditable results including status, summary, repository, and duration for traceability.

How does an admin enforce guardrails for automated code review graph operations?

Admin guardrails are enforced through repository allowlists, input validation, execution timeouts, and sanitized output formatting. This controlled environment prevents accidental changes or data leaks while executing build, impact radius, and review context queries safely.

Can I restrict code review graph queries to specific repositories to prevent data leaks?

Yes, you can restrict code review graph queries by defining an allowlisted repository scope. This feature ensures operations only execute on approved repositories, preventing unauthorized access and accidental data leaks outside the controlled environment.

What is the best way to generate auditable review context for feature flags?

The best way to generate auditable review context is by executing admin-controlled queries that enforce preconditions for feature flags and required inputs. This produces concise, traceable output including repository, status, and duration for review tracking.

What are the limitations of running code review graph operations without timeouts?

Running without timeouts risks unbounded execution and potential system hangs. This Skill mitigates that limitation by enforcing execution timeouts and validating required inputs, ensuring safe boundaries and preventing runaway build or impact radius operations.