rsun-status

Scans git status and client project-state files across multiple repositories into a status report.

Updated May 20, 2026
One-click install
npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill rsun-status-ezonelai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rsun-status
Source: https://github.com/EZoneLai/claude-plugin-ronsunai-os/tree/main/commands/rsun-status
Command: npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill rsun-status-ezonelai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Checking the health of many active projects and client engagements manually means running git commands in every repo and opening each client's state file one by one. This Skill consolidates that into a single structured morning briefing covering both technical repo status and client PM progress. ## Core Features & Use Cases - Multi-repo git scan: Runs git log, status, and cherry across 8 configured repositories to surface recent commits, uncommitted changes, and unpushed work. - Client PM dashboard: Parses project-state.json files per client to show phase, sprint progress, milestone completion, and overdue client-update alerts. - Blocker detection: Flags NEXT_SESSION.md items containing keywords like waiting on approvals or credentials, and escalates overdue client updates to an action list. - Use Case: Start your day by asking for a project status check and receive one report showing which repos have unpushed commits, which clients are overdue for an update, and what the top pending tasks are. ## Quick Start Ask the assistant to check the status of all projects and client engagements for a morning briefing.

Frequently Asked Questions about rsun-status

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

FAQPage Schema
How do I check git status across multiple repositories at once?

Run git log, git status --short, and git cherry against each repo path in a loop, then aggregate the results into one report. This Skill automates that scan across 8 configured project directories and formats the output per repo.

How to track client project milestones in JSON files?

Store per-client state in project-state.json files with phase, milestones, sprint counts, and next update dates. A Python script can glob all state files, compute milestone completion and overdue updates, and print a formatted summary.

Does this Skill commit or push changes automatically?

No. It is strictly read-only: it reports uncommitted files and unpushed commits but never runs commit, push, or deploy commands. Deployment commands are documented for manual use only.

What happens if a repo has no NEXT_SESSION.md file?

The report marks that repo with a 'no NEXT_SESSION' note instead of failing. Similarly, client folders missing project-state.json are labeled as having no PM status, so partial setups still produce a complete report.

How are overdue client updates detected?

The script parses the next_client_update date from each project-state.json and compares it to today. Overdue updates are flagged with the number of days late and escalated into a priority action list at the end of the report.