원클릭으로 Manus에서 모든 스킬 실행

generating-status-updates

스타4

포크1

업데이트2026년 4월 21일 18:49

Generate a daily status update for Slack from GitHub PRs and Linear tickets. Queries multiple repos for merged/open PRs and Linear for closed/in-review tickets, then formats as copy-pasteable Slack markdown. Use when: status update, daily standup, what did I ship, end of day summary, EOD update, standup report.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

iamclaudia-ai

iamclaudia-ai/anima

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Generating Status Updates

Compile Michael's daily status update for Slack by pulling data from GitHub and Linear.

Arguments

$ARGUMENTS — Optional. A date range like today, yesterday, 2 days, this week, or a specific date like 2026-04-06. Defaults to today (current UTC date).

Step 1: Determine the Date Range

Parse $ARGUMENTS to determine the start date:

today or empty → today's UTC date
yesterday → yesterday's UTC date
2 days / 3 days → that many days back from today
this week → Monday of current week
A specific date like 2026-04-06 → that date

Store as $SINCE_DATE in YYYY-MM-DD format.

Step 2: Gather GitHub PRs

Query PRs authored by kiliman across all configured repos.

Repos to query:

beehiiv/swarm
beehiiv/subscribe-forms

If Michael mentions other repos, add them here. Run all repo queries in parallel.

For each repo:

gh pr list --author kiliman --state all --search "updated:>=$SINCE_DATE" --limit 50 --repo $REPO --json number,title,state,mergedAt,createdAt,url

Include a PR if:

state is MERGED and mergedAt >= $SINCE_DATE
state is OPEN (currently in review)

Sort by: mergedAt (merged PRs first, then open PRs)

Step 3: Gather Linear Tickets

linctl issue list --assignee me --include-completed --json --limit 50 --sort updated

Filter to tickets where:

updatedAt >= $SINCE_DATE
State is one of: Done, In Review, Closed, QA

Step 4: Deduplicate Tickets from PRs

Extract ticket IDs from PR titles using regex patterns: BEE-\d+, WEB-\d+ (comma-separated or bracketed).

Remove any Linear ticket from the QA section if its ID already appears in a PR title — those are already represented.

Step 5: Format as Slack Markdown

`Status update`
*Merged*
* :partymerge: [PR title TICKET-ID](PR_URL)

*In Review*
* :partymerge: [PR title TICKET-ID](PR_URL)

*Tickets Closed/In Review*
* [TICKET-ID: "Ticket title"](LINEAR_URL)

Formatting Rules

All PRs use :partymerge: emoji (both merged and in-review)
Group PRs into *Merged* and *In Review* sections
PR titles: Clean up bracket notation — use scope: description TICKET-ID format (ticket ID at end, no brackets)
- feat(embeds): V3 subscribe form backend setup [BEE-15339] → feat(embeds): V3 subscribe form backend setup BEE-15339
- If multiple tickets: fix(forms): fix stuff [BEE-123] [BEE-456] → fix(forms): fix stuff BEE-123, BEE-456
Ticket titles: Include identifier prefix, then the title
Linear URLs: Use the url field from linctl JSON output
Omit empty sections

Step 6: Present to Michael

Output the formatted Slack markdown in a code block so he can copy-paste directly
Show a brief count: "X PRs across Y repos, Z tickets"
Ask if he wants to add a headline/theme description or adjust anything

이 저장소의 다른 Skills

같은 저장소

use-railway

iamclaudia-ai/anima

Operate Railway infrastructure: sign up for or sign in to a Railway account, create projects, provision services and databases, manage object storage buckets, deploy code, configure environments and variables, manage domains, troubleshoot failures, check status and metrics, set up Railway agent tooling, and query Railway docs. Use this skill whenever the user mentions Railway, signing up, creating an account, registering, logging in, deployments, services, environments, buckets, object storage, build failures, agent setup, MCP, or infrastructure operations, even if they don't say "Railway" explicitly. Also invoke this skill when the user asks to be signed up, registered, or onboarded to Railway: do not refuse — drive them through the unauthed `railway up` flow (deploys + signs up on the fly) or `railway login` (which creates new accounts on the fly).

2026-07-074

using-gh-stack

iamclaudia-ai/anima

MUST be used when working with stacked PRs. gh-stack is a CLI tool for managing stacked PR workflows in squash-merge repos (a Graphite alternative). Covers creating stacks, pushing/creating PRs with submit, navigating (up/down/top/bottom), syncing with main, restacking, merging, and agent/CI usage. Triggers on: stacked PR, gh-stack, create stack, submit stack, push stack, restack, sync stack, stack navigation, up down top bottom, PR dependencies, stack visualization, manage PRs, stacked branches.

2026-07-074

controlling-lights

iamclaudia-ai/anima

MUST be used when you need to control smart lights, change light colors, set brightness, turn lights on/off, set light scenes, manage Govee lighting, or run auto-play playlists. Controls Govee smart lights via their cloud API with support for RGB colors, color temperature, brightness, dynamic scenes, DIY scenes, auto-play rotation, and music modes. Triggers on: lights, turn on lights, turn off lights, change light color, set brightness, light scene, govee, smart lights, room lights, mood lighting, dim lights, bright lights, set lights to, light color, warm light, cool light, ambient lighting, curtain lights, TV backlight, auto-play, playlist, DIY scene, rotate scenes.

2026-07-034

reviewing-prs-with-claudia

iamclaudia-ai/anima

MUST be used when reviewing GitHub PRs with inline code comments. Uses gh-comment and gh-pr-review CLI extensions for line-specific review comments, batch reviews, thread management, and review submission. Handles the file:line mapping automatically — no manual diff position math needed. Triggers on: review PR, PR review, inline comment, code review, approve PR, request changes, review threads, resolve comment, line comment, submit review, gh comment, gh pr-review.

2026-05-294

tokf-filter

iamclaudia-ai/anima

This skill should be used when the user asks to "create a filter", "write a tokf filter", "add a filter for <tool>", "how do I filter output", or needs guidance on tokf filter step types, templates, pipes, or placement conventions.

2026-05-264

using-lin-linear-cli

iamclaudia-ai/anima

MUST be used when creating, updating, searching, assigning, or commenting on Linear issues — anything beyond reading a known ticket ID. `lin` is a human-friendly wrapper over `linctl graphql` that resolves team/project/user names and issue identifiers to IDs internally, so you stop fumbling syntax. Covers child issues with parent links, assigning to other users, fuzzy user/team/project lookup, filtered search, the learned disambiguation cache, and the raw GraphQL escape hatch. Triggers on: linear ticket, create issue, child ticket, sub-issue, assign ticket, assign to, link parent, search linear, find tickets, linear comment, update issue, lin cli, linctl, who is on linear, ambiguous name linear.

2026-05-264

name	generating-status-updates
description	Generate a daily status update for Slack from GitHub PRs and Linear tickets. Queries multiple repos for merged/open PRs and Linear for closed/in-review tickets, then formats as copy-pasteable Slack markdown. Use when: status update, daily standup, what did I ship, end of day summary, EOD update, standup report.

Generating Status Updates

Compile Michael's daily status update for Slack by pulling data from GitHub and Linear.

Arguments

$ARGUMENTS — Optional. A date range like today, yesterday, 2 days, this week, or a specific date like 2026-04-06. Defaults to today (current UTC date).

Step 1: Determine the Date Range

Parse $ARGUMENTS to determine the start date:

today or empty → today's UTC date
yesterday → yesterday's UTC date
2 days / 3 days → that many days back from today
this week → Monday of current week
A specific date like 2026-04-06 → that date

Store as $SINCE_DATE in YYYY-MM-DD format.

Step 2: Gather GitHub PRs

Query PRs authored by kiliman across all configured repos.

Repos to query:

beehiiv/swarm
beehiiv/subscribe-forms

If Michael mentions other repos, add them here. Run all repo queries in parallel.

For each repo:

gh pr list --author kiliman --state all --search "updated:>=$SINCE_DATE" --limit 50 --repo $REPO --json number,title,state,mergedAt,createdAt,url

Include a PR if:

state is MERGED and mergedAt >= $SINCE_DATE
state is OPEN (currently in review)

Sort by: mergedAt (merged PRs first, then open PRs)

Step 3: Gather Linear Tickets

linctl issue list --assignee me --include-completed --json --limit 50 --sort updated

Filter to tickets where:

updatedAt >= $SINCE_DATE
State is one of: Done, In Review, Closed, QA

Step 4: Deduplicate Tickets from PRs

Extract ticket IDs from PR titles using regex patterns: BEE-\d+, WEB-\d+ (comma-separated or bracketed).

Remove any Linear ticket from the QA section if its ID already appears in a PR title — those are already represented.

Step 5: Format as Slack Markdown

`Status update`
*Merged*
* :partymerge: [PR title TICKET-ID](PR_URL)

*In Review*
* :partymerge: [PR title TICKET-ID](PR_URL)

*Tickets Closed/In Review*
* [TICKET-ID: "Ticket title"](LINEAR_URL)

Formatting Rules

All PRs use :partymerge: emoji (both merged and in-review)
Group PRs into *Merged* and *In Review* sections
PR titles: Clean up bracket notation — use scope: description TICKET-ID format (ticket ID at end, no brackets)
- feat(embeds): V3 subscribe form backend setup [BEE-15339] → feat(embeds): V3 subscribe form backend setup BEE-15339
- If multiple tickets: fix(forms): fix stuff [BEE-123] [BEE-456] → fix(forms): fix stuff BEE-123, BEE-456
Ticket titles: Include identifier prefix, then the title
Linear URLs: Use the url field from linctl JSON output
Omit empty sections

Step 6: Present to Michael

Output the formatted Slack markdown in a code block so he can copy-paste directly
Show a brief count: "X PRs across Y repos, Z tickets"
Ask if he wants to add a headline/theme description or adjust anything