daily-summary

Create a daily GitHub Issue summarizing yesterday's commits and PRs.

2|Updated May 2, 2026
One-click install
npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill daily-summary-andrecini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-summary
Source: https://github.com/andrecini/dotnet-squad-copilot-agent/tree/main/.claude/skills/daily-summary
Command: npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill daily-summary-andrecini

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git.

What problem does it solve?

It saves teams time by generating and creating an asynchronous “daily” GitHub Issue that summarizes yesterday’s work, so members don’t have to compile updates manually.

Core Features & Use Cases

  • Auto-detect activity from Git and GitHub: Collects commits, PRs, and issue movements from the previous day to build an activities section.
  • Create the daily issue with a consistent template: Uses a predefined agile ceremony context and applies the restricted label policy.
  • Safe fallback for API failures: Produces the complete title/body for manual issue creation if GitHub API calls fail.
  • Use case: When a team needs a daily status workflow, you can request creation of “Daily — DD/MM/YYYY” and get a ready-to-post issue with detected activity or a blank/manual template.

Quick Start

Ask an AI to create the daily issue for today using the daily-summary skill, automatically detecting yesterday’s commits, PR updates, and issue changes when available.

Frequently Asked Questions about daily-summary

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

FAQPage Schema
How do I automate daily status issues from GitHub activity?

You need the 'gh' and 'git' command-line tools installed and configured in your repository. This Skill relies on them to detect prior-day Git commits and GitHub PRs, ensuring accurate activity data extraction before generating the daily issue.

How does async daily issue generation handle GitHub API failures?

When GitHub API creation fails during async daily issue generation, the Skill provides a safe fallback by producing the complete title and body text. This allows you to manually copy and paste the daily summary into a new issue without losing the detected activity data.

Can I use this to create sprint planning or retrospective cards?

No, you cannot use this for sprint planning, retrospectives, or generic card creation. The Skill restricts operations to generating only daily 'Daily — DD/MM/YYYY' issues labeled 'chore', specifically summarizing yesterday's repository activity for asynchronous team updates.

How do I create a daily summary issue with yesterday's commits and PRs?

To create a daily summary issue with yesterday's commits and PRs, request the Skill to 'create the daily issue for today'. It will automatically detect prior-day Git and GitHub activity and populate a predefined agile ceremony template with the results.