checkup

Identifies Git repository health issues across worktrees, branches, and remotes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/oobagi/jflow --skill checkup-oobagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkup
Source: https://github.com/oobagi/jflow/tree/main/skills/checkup
Command: npx skills add https://github.com/oobagi/jflow --skill checkup-oobagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining a Git repository can accumulate stale worktrees, stale branches, and hygiene gaps that slow development or cause confusion. This skill runs comprehensive checks and surfaces issues before they disrupt work.

Core Features & Use Cases

  • Parallel information gathering across git state (worktrees, branches, remotes) for fast feedback
  • Identify stale worktrees and branches with clear indicators and suggested actions
  • Safeguarded cleanup planning that asks for confirmation (or runs immediately with now)
  • Generates a clear health report you can act on in future sessions

Quick Start

Run the checkup to scan your repository and see recommended actions; you can apply them by passing the now flag.

Frequently Asked Questions about checkup

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

FAQPage Schema
How do I clean up stale git worktrees and branches in my local repository?

To clean up stale git worktrees and branches, run a repository checkup to identify hygiene gaps and apply suggested actions. You can execute cleanup immediately by providing the now flag, or review proposed actions with confirmation prompts.

What is the best way to check git repository health across multiple remotes?

Checking git repository health across multiple remotes involves parallel information gathering on worktrees, branches, and remote states. This process validates default branches and surfaces integrity issues before they disrupt your development workflow.

Can I automate git repo cleanup without manual confirmation for every action?

Yes, you can automate git repo cleanup without manual confirmation by passing the now flag. This bypasses the safeguard confirmation prompts and immediately executes the proposed cleanup actions for stale worktrees and branches.

Does this git cleanup tool work with any local clone or workspace workflow?

Yes, this git cleanup tool works with any local clone or workspace workflow. It supports scenarios like cleaning stale worktrees, pruning branches, and verifying repository integrity without requiring specific dependencies.

Why do I need to validate default branches during a git repository health check?

Validating default branches during a git repository health check ensures remote integrity and prevents confusion caused by misconfigured upstreams. This safeguard is applied during parallel information gathering across remotes.

What git hygiene issues should I look for before running a repository cleanup?

Git hygiene issues to look for include stale worktrees, unpruned branches, and remote configuration gaps. A repository checkup surfaces these issues by scanning git state in parallel and generating a clear health report.