skills.rest
Yoodaddy0311
Yoodaddy0311COMMUNITY
Explore all skills by this author →
GitHub

daily

Generates an end-of-day retrospective dashboard summarizing commits, quality signals, work status, and next steps.

3|2|Updated Feb 13, 2026
Search Tags:#standup#git commits#work summary#worklog#recap#daily retrospective#quality status
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill daily-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daily
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/daily
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill daily-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? At the end of a workday, developers often struggle to recall what they committed, what quality checks passed or failed, and what should come next. This Skill automates the daily retrospective by collecting git activity, quality signals, and work status into a structured six-section dashboard. ## Core Features & Use Cases - Commit and Change Summary: Collects today's git activity and summarizes changed files and affected areas. - Quality and Status Reporting: Checks test, lint, and coverage signals alongside in-progress, completed, and pending work. - Prioritized Next Steps: Distills key decisions from worklogs or session notes and proposes actionable next steps with rationale. - Use Case: Before logging off, ask for a daily recap and receive a compact dashboard covering today's commits, failing tests, unresolved issues, and tomorrow's priorities. ## Quick Start Ask the assistant to generate a daily retrospective of today's commits, quality status, and next steps.

Frequently Asked Questions about daily

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

FAQPage Schema
How do I generate a daily work summary from git commits?▼

Invoke the daily retrospective at the end of your workday. It collects today's git activity, summarizes changed files and areas, and combines them with quality signals and work status into a six-section dashboard.

What sections does a daily retrospective report include?▼

The report contains six sections: today's commit summary, changed files and areas, quality status, work status, key decisions and notes, and next steps. Each next step includes a priority and rationale.

Can I use a daily recap for standup meeting preparation?▼

Yes, the dashboard format maps well to standup updates since it covers completed work, blockers, and next steps. Unlike a verbal standup, it also preserves decisions and context as a durable written record.

Does the daily summary work in Korean or other languages?▼

The skill supports English and Korean, with triggers in both languages such as 회고, 일일 보고, and retrospective. It is also listed as compatible with Claude Code, Gemini CLI, Codex CLI, and Cursor.

When should I not use a daily retrospective skill?▼

Avoid it for mid-session task execution or detailed technical investigation. It is designed for end-of-day summaries, not real-time work tracking or deep debugging sessions.

What happens if there is no activity to summarize today?▼

The skill does not guess or fabricate content. Missing information is explicitly marked as unconfirmed, and blockers or idle days are documented as valid work status rather than hidden.

Related Skills

Explore More Software Engineering Skills→
noontide-conoontide-co
35

mb-end

Compile session activity and spawn a subagent to crystallize insights.

Official
Advanced
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate
polikeijipolikeiji

implement-ticket

Implement GitHub project tickets end-to-end and open a linked pull request.

Community
Advanced
maggitmaggit

standup

Parse git logs and group commits into a markdown standup report.

Community
Intermediate