briefing

Generates a daily briefing summarizing commits, TODOs, pending PRs, and test results from the current repository state.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/manastalukdar/ai-devstudio --skill briefing-manastalukdar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: briefing
Source: https://github.com/manastalukdar/ai-devstudio/tree/main/skills/briefing
Command: npx skills add https://github.com/manastalukdar/ai-devstudio --skill briefing-manastalukdar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, up-to-date briefing that consolidates recent git activity, open TODOs, pending PRs, failing tests, and current session context so developers can start work immediately.

Core Features & Use Cases

  • Consolidates recent commits, pull requests, and test results into a single digest.
  • Includes open TODOs and session context to guide daily planning.
  • Omit empty sections to keep the briefing succinct and actionable.

Quick Start

Run the briefing skill to generate today's briefing from your current repository state.

Frequently Asked Questions about briefing

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

FAQPage Schema
How do I generate a daily developer briefing from git activity and open TODOs?

A daily developer briefing consolidates recent git commits, open TODOs, pending pull requests, and test results into a scannable card format. It applies bash-based data collection across your current workspace to provide immediate situational awareness.

Can I get a summary of recent commits and pending PRs in a single digest?

Yes, you can summarize recent commits and pending PRs in a single digest by running a workspace briefing. It applies conditional section rendering to omit empty data points, keeping the report scannable and actionable.

What is the best way to track failing tests and session state for daily planning?

Tracking failing tests and session state for daily planning is best handled by a repository activity briefing. It consolidates current workspace context and test results to guide developers in starting work immediately.

Does this daily workflow briefing require any external dependencies to parse repository data?

No external dependencies are required to parse repository data for the daily workflow briefing. It relies entirely on bash-based data collection mechanisms to extract commits, PRs, and TODOs from the current local workspace.

How to keep a git workflow digest succinct when there are no pending pull requests?

To keep a git workflow digest succinct when there are no pending pull requests, the briefing applies conditional section rendering. This automatically omits empty sections like missing PRs or failing tests to produce a concise report.

Why does my daily session management briefing show empty test result sections?

A daily session management briefing shows empty test result sections when conditional rendering is applied to omit missing data. If no failing tests are detected during the bash data collection, the section is excluded for brevity.