eod

Scan configured git repos for uncommitted and unpushed work.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/LarryHsiao/Skadi --skill eod-larryhsiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eod
Source: https://github.com/LarryHsiao/Skadi/tree/main/skills/eod
Command: npx skills add https://github.com/LarryHsiao/Skadi --skill eod-larryhsiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Researchers or developers need a quick, reliable sweep of configured repositories to surface uncommitted or unpushed work before logging off to prevent loss. This skill automates that check and summarization.

Core Features & Use Cases

  • Scans configured project repos for git state: uncommitted, unpushed, and related signals.
  • Renders a concise report per repo and suggests next steps for clean state.
  • Use case: as part of end-of-day routine, you ensure nothing is left behind, or before a handover in a team.

Quick Start

Ask for project roots when needed, run the git check, render the report, and suggest the next steps.

Frequently Asked Questions about eod

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

FAQPage Schema
How do I check multiple git repositories for uncommitted changes before logging off?

Checking unpushed commits across git repositories involves scanning multiple local workspaces and corporate roots to render a structured report, ensuring safe pre-approved git checks before logging off.

What is the best way to scan local workspaces for unpushed commits?

Scanning local workspaces for unpushed commits requires a sweep across configured project roots that identifies uncommitted work and renders a concise report with suggested next steps for a clean state.

Can I use this git check across corporate repositories and local workspaces?

Yes, you can run this git check across both local workspaces and corporate repositories by configuring multiple project roots, allowing the end-of-day sweep to identify unfinished work across all specified directories.

How do I get a structured report of uncommitted work across my project roots?

To get a structured report of uncommitted work, the skill scans your configured project roots and renders a concise per-repo summary, prompting you for missing roots when needed to complete the sweep.

What should I do if a project root is missing during an end-of-day git sweep?

If a project root is missing during your end-of-day git sweep, the skill will prompt you to provide the missing roots before running the git check, ensuring all relevant repositories are scanned for uncommitted work.