code-chief

Orchestrate multi-phase code reviews for repositories and pull requests.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill code-chief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-chief
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/review/code-chief
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill code-chief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code-chief eliminates fragmented, single-pass code reviews by orchestrating a structured, multi-phase review pipeline that enforces correctness, maintainability, security, adversarial testing, and frontend audits while providing traceable saves and resumable state. It reduces risk by ensuring every deliverable is validated through adversarial gatekeepers before delivery and by consolidating cross-skill findings into an auditable review package.

Core Features & Use Cases

  • Full Pipeline Orchestration: Drives a canonical sequence of review phases (bug-review, code-review, quality-review, security-review, mr-robot, frontier) and enforces mandatory phases and skip logic.
  • Gatekeeper Management: Submits consolidated packages to adversarial gatekeepers, manages revision cycles, and enforces maximum revision rules and escalation paths.
  • Persistence & Resume: Creates structured save artifacts, session locking, heartbeat management, and resume logic for cross-session continuation and audit trails.
  • Delegation Templates & Protocols: Produces standardized delegation requests and machine-readable summaries for each specialist skill, ensuring consistent inputs and outputs.
  • Use Case: Run a comprehensive audit of a repository, a PR, or a module to receive an evidence-backed, consolidated review package with prioritized remediation and disputed-item records.

Quick Start

Ask code-chief to run a full pipeline code review on the target repository or pull request and deliver the consolidated validated review package.

Frequently Asked Questions about code-chief

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

FAQPage Schema
How do I orchestrate a multi-phase code review pipeline for a pull request?

Multi-phase code review pipelines are orchestrated by delegating to specialist review skills, managing gatekeeper validation cycles, and applying skip logic to produce a consolidated, validated review package for pull requests and changesets.

What is an end-to-end code review pipeline and when do I need it for a repository?

An end-to-end code review pipeline sequences bug, quality, security, and adversarial testing phases to validate deliverables. You need it for repository audits or targeted changesets to ensure evidence-backed, consolidated remediation with audit trails.

Can I resume an interrupted code review session and maintain persistence?

Yes, interrupted code review sessions can be resumed using structured save artifacts, session locking, and heartbeat management, which provide cross-session continuation and full audit trails for the review state.

How do gatekeeper validation cycles work in a structured code review?

Gatekeeper validation cycles submit consolidated review packages to adversarial gatekeepers, manage revision cycles, enforce maximum revision rules, and trigger escalation paths to ensure correctness and security before delivery.

What's the best way to consolidate findings from separate security and code quality reviews?

Consolidating findings from separate security and code quality reviews is best handled by orchestrating delegation templates that produce machine-readable summaries, which are then merged into an auditable review package with prioritized remediation.

What are the limitations of using a delegated code review orchestration pipeline?

Limitations of delegated code review orchestration pipelines include dependency on specialist review skills for each phase and strict adherence to maximum revision rules, which may trigger escalation paths if gatekeepers repeatedly reject deliverables.