daily-updates

Aggregate GitHub PRs, Linear tickets, Slack messages, and Conductor notes into daily standup updates.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Alfie728/my-skills --skill daily-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-updates
Source: https://github.com/Alfie728/my-skills/tree/main/daily-updates
Command: npx skills add https://github.com/Alfie728/my-skills --skill daily-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers spend time stitching together pull requests, issue tracker updates, chat discussions, and local session notes to produce a short status update for leadership. This Skill automates that synthesis and produces a focused, CTO-facing summary so the engineer can send a clear daily report without manual aggregation.

Core Features & Use Cases

  • Multi-source aggregation: Pulls GitHub PR activity, Linear ticket changes, Slack mentions and messages, and Conductor workspace session notes to form a single view of daily work.
  • Cross-referencing: Links PRs to Linear issue IDs and related Slack or Conductor context so each bullet reflects outcome and status, not implementation detail.
  • Concise output for leadership: Drafts 3-5 short bullet points organized by status (Merged, In Progress, In Review) tailored for Tarun to quickly understand progress.
  • Use case: Generate a one-paragraph, 3-5 bullet standup for today's work highlighting merged PRs, tickets completed, and items in review.

Quick Start

Ask daily-updates to draft a concise daily standup for Tarun for today or a specific date.

Frequently Asked Questions about daily-updates

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

FAQPage Schema
How do I generate a daily standup update from GitHub PRs and Linear tickets?

Generate a daily standup update by aggregating merged GitHub PRs, Linear ticket changes, Slack messages, and Conductor notes into 3-5 concise bullets organized by Merged, In Progress, and In Review statuses for leadership.

Can I cross-reference Slack messages with Linear issues for a status report?

Yes, you can cross-reference Slack messages with Linear issues and GitHub PRs. The aggregation links PRs to Linear issue IDs and related chat context so each status report bullet reflects outcome and status rather than implementation detail.

What is the best way to summarize daily engineering progress for a CTO?

The best way to summarize daily engineering progress for a CTO is drafting a focused, 3-5 bullet point report covering merged work, in-progress items, and reviews, synthesized automatically from your GitHub, Linear, and Slack activity.

Do I need Conductor session notes to draft a daily status update?

Conductor session notes are used to cross-reference ticket IDs and add local context to your daily status update. You need access to Conductor workspace notes, alongside GitHub PR metadata, Linear updates, and Slack history, to craft the most accurate report.

How does multi-source aggregation work for automated standup reports?

Multi-source aggregation works by pulling GitHub PR activity, Linear ticket changes, Slack mentions, and Conductor session notes to form a single view of daily work, cross-referencing ticket IDs to produce concise leadership-facing status bullets.

Are there limitations when formatting daily updates from multiple project management tools?

A limitation is that generating the daily update requires access to GitHub PR metadata, Linear issue updates, Slack message history, and local Conductor workspace notes simultaneously to cross-reference ticket IDs and accurately draft the standup summary.