brief

Name: brief
Availability: InStock
Author: ChazzCoin

Aggregate commits, pull requests, and state changes into a CTO briefing.

Updated May 7, 2026

Search Tags:#state tracking #codebase overview #briefing #change summary #CTO dashboard

Ready to run

npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill brief-chazzcoin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/brief
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill brief-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a concise, CTO-level briefing on recent changes and open issues across all sub-repositories, ensuring you're up-to-date with the state of the company's codebase without diving into details.

Core Features & Use Cases

Summary of Recent Changes: Provides a snapshot of commits, open pull requests, and changes in the state of sub-repositories.
Open Migrations and Risks: Lists active migrations and risks that need attention.
Incidents and Questions: Summarizes recent incidents and questions raised by the team.
Use Case: At the start of a new day or week, use this Skill to quickly understand what has changed and what needs attention across all your sub-repositories.

Quick Start

Use the brief skill to get a rundown of recent changes and open issues across all sub-repositories.

Frequently Asked Questions about brief

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

FAQPage Schema

How do I get a CTO dashboard summary of recent codebase changes across sub-repos?▼

A briefing on recent changes requires local repository state, orchestrator state, and access to GitHub pull requests. You must ensure these data sources are accessible before generating the summary of commits, migrations, and incidents.

What is the best way to track open migrations and incidents across multiple repositories?▼

A briefing aggregates state tracking data and orchestrator state to identify active migrations and incidents. It provides a dashboard view of open risks and recent team questions across all sub-repositories.

How do I generate a change summary for multiple sub-repositories at once?▼

This skill synthesizes a change summary by aggregating local repository state and GitHub pull requests across sub-repositories. It compiles commits, open pull requests, and state file changes into a unified briefing.

Can I use this briefing tool to track recent team questions and incidents?▼

Yes, you can use this briefing tool to track recent team questions and incidents. It aggregates state files and orchestrator data to summarize incidents and questions raised by the team.

Does this codebase overview tool work without GitHub pull request access?▼

No, this codebase overview tool requires access to GitHub pull requests. It also needs local repository state and orchestrator state to synthesize the briefing.

Why does my state tracking briefing fail to aggregate sub-repository changes?▼

Your state tracking briefing may fail if local repository state or orchestrator state is missing. Ensure you have proper access to GitHub pull requests and that state files are correctly configured.