global-review-loop

Name: global-review-loop
Availability: InStock
Author: Bryce

Analyzes Claude Code CLI and Cowork transcripts to identify recurring cross-project friction and propose global ~/.claude config changes.

Updated Jun 16, 2026

Search Tags:#cross-project #ledger #friction-analysis #global-review-loop #fleet-analysis #privacy-guard

Ready to run

npx skills add https://github.com/BryceEWatson/claude-global-skills --skill global-review-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: global-review-loop
Source: https://github.com/BryceEWatson/claude-global-skills/tree/main/global-review-loop
Command: npx skills add https://github.com/BryceEWatson/claude-global-skills --skill global-review-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cross-project friction across multiple Claude projects slows delivery and consistency. This Skill identifies recurring issues across the fleet and surfaces proposals to fix them at the global Claude config surface.

Core Features & Use Cases

Fleet-wide friction mining across Claude Code CLI and Cowork corpora, with path-attributed evidence to ensure accurate cross-project counting.
Global-proposal generation and reconciliation against existing surfaces, backed by a private ledger for auditable loop closure.
Use cases include discovering friction that recurs in two or more distinct projects and proposing minimal, globally-scoped changes to ~/.claude.

Quick Start

Copy the global-review-loop skill into your Claude Code skills folder and invoke /global-review-loop.

Frequently Asked Questions about global-review-loop

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

FAQPage Schema

How do I identify recurring friction across multiple Claude Code projects?▼

To identify recurring friction across multiple projects, you can mine Claude Code CLI and Cowork transcripts fleet-wide. This process counts path-attributed evidence to pinpoint issues occurring in two or more distinct projects.

What is the best way to improve global Claude configuration based on cross-project issues?▼

Improving global Claude configuration from cross-project issues involves generating proposals for minimal changes to the ~/.claude surface. A private ledger and formal upsert workflow ensure these global updates are deliberate and auditable.

How do I track and audit changes to my Claude config surface?▼

You can track and audit changes to the Claude config surface by using a cross-run ledger and a formal upsert/claim workflow. This enforces safety and ensures that all global configuration updates are deliberate and traceable.

Can I analyze Claude Code CLI transcripts without exposing private project data?▼

Yes, you can analyze CLI transcripts while protecting data by enforcing safety with privacy guards. This ensures the fleet-wide friction mining process does not expose sensitive project information during cross-run analysis.

Does global-review-loop work with Cowork transcripts for fleet analysis?▼

Yes, global-review-loop performs fleet analysis on both Claude Code CLI and Cowork transcripts. It consolidates recurring friction across these corpora using path-attributed evidence to propose globally scoped configuration changes.