ワンクリックでManusで任意のスキルを実行

standup

スター0

フォーク0

更新日2026年5月6日 07:01

Create concise repository standup summaries from git state, GitHub issues, and pull requests. Use when asked for standup, status summary, upcoming work, in-progress tasks, blockers, or repo progress.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ralphschuler

ralphschuler/pi-agent-setup

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Standup

Create a concise read-only standup summary for a repository.

Use human_in_loop for every user-facing clarification or approval question. Do not ask those questions in plain assistant text.

Rules

Stay read-only: do not modify files, issues, PRs, branches, labels, or remote state.
Use the current repository only unless the user explicitly asks for another repo.
If gh is unavailable or unauthenticated, report setup blockers instead of fabricating GitHub state.
Prefer evidence from git and GitHub CLI over memory.
Include links for referenced issues and PRs.
Keep the final summary concise and action-oriented.

Workflow

Inspect local repo state:
- git status --short --branch
- git branch --show-current
- git remote -v
- default branch from git remote show origin
- git log --oneline --decorate -n 10
Inspect GitHub auth and repo:
- gh auth status
- gh repo view --json nameWithOwner,url,defaultBranchRef
Inspect GitHub work:
- gh issue list --state open --limit 50 --json number,title,labels,updatedAt,url,assignees
- gh issue list --state closed --limit 20 --json number,title,closedAt,url
- gh pr list --state open --limit 50 --json number,title,headRefName,isDraft,updatedAt,url,statusCheckRollup,closingIssuesReferences
- gh pr list --state merged --limit 20 --json number,title,mergedAt,url,closingIssuesReferences
Use gh issue view or gh pr view for high-priority, blocked, ambiguous, or active items.
Classify:
- completed/recently merged or closed
- today/in progress
- blockers/risks
- upcoming priorities ordered by dependency and actionability
- repo hygiene
If scope/date range is ambiguous and materially affects output, ask one concise human_in_loop question with a recommended default.
Output the standup summary.

Output template

## Standup — <repo> — <date>

### Yesterday / Completed

- ...

### Today / In progress

- ...

### Blockers / Risks

- ...

### Upcoming / Next priorities

1. ...

### Repo hygiene

- Branch: ...
- Working tree: ...
- PR checks: ...

### Links

- Issues: ...
- PRs: ...

このリポジトリの他の Skills

同じリポジトリ

pi-subagents

ralphschuler/pi-agent-setup

Delegate bounded work to this package's custom subagent tool. Use for specialist reconnaissance, planning, research, implementation handoffs, and independent review when parallel context or separation of concerns helps.

2026-07-140

systematic-debugging

ralphschuler/pi-agent-setup

Diagnose and fix bugs with a disciplined evidence-first workflow. Use when investigating failing tests, runtime errors, regressions, flaky behavior, performance issues, or unclear root causes.

2026-05-080

implement

ralphschuler/pi-agent-setup

Implement features or fixes with behavior-first tests, vertical TDD slices, validation, and rollback notes. Use when asked to build, change, fix, or complete implementation work.

2026-05-080

pi-processes

ralphschuler/pi-agent-setup

Manage long-running commands with this package's custom process tool. Use for dev servers, test watchers, build watchers, local APIs, preview servers, and log tails that should keep running while work continues.

2026-05-070

github-merge

ralphschuler/pi-agent-setup

Safely merge an existing GitHub PR by waiting for checks and using a rebase merge. Use when asked to merge a PR, current branch, or `/merge` workflow.

2026-05-070

pi-resource-design

ralphschuler/pi-agent-setup

Design Pi prompt templates, skills, extensions, tools, and custom subagents using the repository resource ruleset.

2026-05-060

Standup

Create a concise read-only standup summary for a repository.

Use human_in_loop for every user-facing clarification or approval question. Do not ask those questions in plain assistant text.

Rules

Stay read-only: do not modify files, issues, PRs, branches, labels, or remote state.

Use the current repository only unless the user explicitly asks for another repo.

If gh is unavailable or unauthenticated, report setup blockers instead of fabricating GitHub state.

Prefer evidence from git and GitHub CLI over memory.

Include links for referenced issues and PRs.

Keep the final summary concise and action-oriented.

Workflow

Inspect local repo state:

git status --short --branch
git branch --show-current
git remote -v
default branch from git remote show origin
git log --oneline --decorate -n 10

Inspect GitHub auth and repo:

gh auth status
gh repo view --json nameWithOwner,url,defaultBranchRef

Inspect GitHub work:

gh issue list --state open --limit 50 --json number,title,labels,updatedAt,url,assignees
gh issue list --state closed --limit 20 --json number,title,closedAt,url
gh pr list --state open --limit 50 --json number,title,headRefName,isDraft,updatedAt,url,statusCheckRollup,closingIssuesReferences
gh pr list --state merged --limit 20 --json number,title,mergedAt,url,closingIssuesReferences

Use gh issue view or gh pr view for high-priority, blocked, ambiguous, or active items.

Classify:

completed/recently merged or closed
today/in progress
blockers/risks
upcoming priorities ordered by dependency and actionability
repo hygiene

If scope/date range is ambiguous and materially affects output, ask one concise human_in_loop question with a recommended default.

Output the standup summary.

Output template

## Standup — <repo> — <date> ### Yesterday / Completed - ... ### Today / In progress - ... ### Blockers / Risks - ... ### Upcoming / Next priorities 1. ... ### Repo hygiene - Branch: ... - Working tree: ... - PR checks: ... ### Links - Issues: ... - PRs: ...

name	standup
description	Create concise repository standup summaries from git state, GitHub issues, and pull requests. Use when asked for standup, status summary, upcoming work, in-progress tasks, blockers, or repo progress.