z

Aggregate repository status signals into a concise health snapshot.

1|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bettercallzaal/ZAOOS --skill z-bettercallzaal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: z
Source: https://github.com/bettercallzaal/ZAOOS/tree/main/.claude/skills/z
Command: npx skills add https://github.com/bettercallzaal/ZAOOS --skill z-bettercallzaal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface the health and readiness of a repository by aggregating key status signals into a concise dashboard, saving time during development sprints and reviews.

Core Features & Use Cases

  • Parallel collection of: current branch, recent commits, git status, unpushed commits, local server status, build directory presence, research folder count, open/merged PRs, and deployment status.
  • Use during development, code reviews, and sprint demos to get a one-page health snapshot of the project.
  • Provides a deterministic, quick-check workflow that can be extended with additional signals as needed.

Quick Start

Use the z skill to generate a fast, concise repository health snapshot for your current project.

Frequently Asked Questions about z

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

FAQPage Schema
How do I check repository health and status signals quickly?

A repository health snapshot aggregates branch, git status, unpushed commits, build directory, and deployment status signals in parallel. It runs read-only data collection to produce a concise, decision-ready report for development sprints and code reviews.

What is included in a repository health snapshot?

A repository health snapshot includes current branch, recent commits, git status, unpushed commits, local server status, build directory presence, research folder count, open PRs, and deployment status. These signals are collected in parallel and formatted deterministically.

Can I use a repository health dashboard for CI checks and code reviews?

Yes, a repository health dashboard is applicable to CI checks and code reviews. It enforces read-only data collection to safely aggregate status signals, providing a compact, decision-ready report without modifying the repository state.

What's the best way to aggregate unpushed commits and PR status for a sprint demo?

The best way to aggregate unpushed commits and PR status is running parallel signal collection across repository metrics. This surfaces a deterministic, one-page health snapshot summarizing project readiness for sprint demos and reviews.

Does repository health monitoring modify my local development environment?

No, repository health monitoring enforces read-only data collection. It aggregates status signals like local server status and build directory presence without modifying your local development environment or repository state.