dev-brief

Generates morning briefs of TODOs, git state, and session logs across projects.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill dev-brief-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-brief
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/dev-brief
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill dev-brief-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers juggling multiple projects lose context between sessions and forget open TODOs, unpushed commits, and past decisions. This Skill sweeps every project in ~/dev and produces a prioritized morning or context-switch brief so you can resume work immediately. ## Core Features & Use Cases - Cross-project sweep: Discovers all projects in ~/dev, reads TODOS.md or session logs, and reports branch, uncommitted files, unpushed commits, staleness, and release-pending signals per project. - Auto-reconciliation: Compares open TODOs against live git state and auto-resolves items like "push commits" or "commit changes" when git shows the work is done, with advisory fix-commit flags for possibly-resolved bugs. - Priority triage: Tiers every open TODO from Critical to Backlog using tags and keyword fallback, with an mtime-based cache to skip unchanged logs. - Use Case: Run /dev-brief on Monday morning to see all open TODOs across your repos tiered by urgency, then run /dev-brief myproject for a deep-dive with a ready-to-paste re-entry prompt. ## Quick Start Ask the AI to run /dev-brief to generate a prioritized brief of TODOs and git state across all projects in ~/dev.

Frequently Asked Questions about dev-brief

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

FAQPage Schema
How do I get a summary of open TODOs across multiple git projects?▼

Run /dev-brief to sweep every project in ~/dev. It reads TODOS.md or session logs per project and outputs open TODOs tiered from Critical to Backlog, plus branch, uncommitted, and unpushed counts.

How to resume work on a project after a context switch?▼

Run /dev-brief <project> for a deep-dive on a single project. It shows tiered TODOs, gotchas, decisions, and a self-contained re-entry prompt you can paste as your first message to resume the session.

Can TODOs be auto-resolved based on git state?▼

Yes. The Skill compares open TODOs against live git status and unpushed commit counts, auto-resolving items like "push to remote" or "commit changes" when git confirms completion. Fix-commit flags for bugs are advisory only and never written.

Does the brief work with projects that have no TODO file?▼

Projects without TODOS.md are parsed from their session-log latest block instead. Directories with neither a TODO file nor a session log are listed as orphans at the bottom of the brief.

Why does the brief skip reading some session logs?▼

An mtime-based cache gate skips logs unchanged since the last run, loading open TODOs from the triage cache instead. Git state is always fetched live and never cached, so branch and commit counts stay current.