standup-summary
Skill2 starsChanged 20 days agoApache-2.0View on GitHub
Generate a standup summary from recent activity - git commits, Jira issues, MRs, calendar, Slack, memory follow-ups, discovered work. Use when user says "standup", "generate standup", "what did I do?", or "daily status".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- mergisi/awesome-openclaw-agentstheir own version, first seen Nov 1, 2026
- Suryanandx/qvac-uitheir own version, first seen Nov 1, 2026
- jholhewres/devclaw-skillstheir own version, first seen Oct 9, 2026
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
- Iloveiaverymuch/claude-skillstheir own version, first seen May 27, 2026
- nimbalyst/skillstheir own version, first seen Feb 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- nimbalyst/skills★ 28same name
- KhaledSaeed18/dotclaude★ 5same name
- jholhewres/devclaw-skills★ 4same name
- Iloveiaverymuch/claude-skills★ 0same name
- Suryanandx/qvac-ui★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Repo resolution: Use repo if given; else repo_name from config.json → repositories.
- Very specific: line 42
Use inputs.author if provided
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Standup Summary
Produces a formatted markdown standup with What I Did, What I'm Working On, meetings, team channel, blockers, AI status, follow-ups, and discovered work.
Inputs
| Input | Type | Default | Purpose |
repo | string | — | Repository path |
repo_name | string | — | Config key (e.g. automation-analytics-backend) |
issue_key | string | — | Resolve repo from Jira project (e.g. AAP-12345 → AAP) |
days | int | 1 | Days back for commits/Jira |
include_jira | bool | true | Include Jira section |
include_gitlab | bool | true | Include GitLab MR section |
author | string | — | Override git author (default: git config) |
slack_format | bool | false | Use <url|text> for links |
Repo resolution: Use repo if given; else repo_name from config.json → repositories; else issue_key → project prefix → matching repo; else cwd if git repo.
Persona Switches
- developer: Git, Jira, GitLab, Gmail, performance
- meetings:
google_calendar_list_events - slack:
slack_find_channel,slack_list_messages
Workflow
1. Bootstrap
persona_load("developer")check_known_issues("gitlab_mr_list")check_known_issues("jira_search")
2. Resolve Repo & Author
- Resolve
repo_path,gitlab_project,jira_projectfrom inputs +config.json git_config_get(repo, key="user.email")— author emailgit_config_get(repo, key="user.name")— author name- Use
inputs.authorif provided
3. Git Commits
git_log(repo=repo_path, limit=30, oneline=true)- Parse output: extract sha, message; extract Jira keys (e.g. AAP-12345) from messages
4. Calendar
persona_load("meetings")google_calendar_list_events(days=1)- Parse: time, title for today's events
5. Slack
persona_load("slack")slack_find_channel(query="team-automation-analytics")slack_list_messages(channel_id=..., limit=20)- Parse recent messages (first 10)
6. Jira (if include_jira)
persona_load("developer")jira_my_issues(max_results=20)jira_search(jql='project = {jira_project} AND assignee = currentUser() AND status in ("In Progress", "In Review") ORDER BY updated DESC')jira_search(jql='project = {jira_project} AND assignee = currentUser() AND status = Done AND updated >= -{days}d ORDER BY updated DESC')- Parse: key, summary for in-progress and done
7. GitLab (if include_gitlab)
gitlab_mr_list(project=gitlab_project, state="all", author=author_name)— my MRsgitlab_mr_list(project=gitlab_project, state="all", reviewer=author_name)— reviewed- Parse: iid, title (e.g.
!1452pattern)
8. Optional Context
gmail_unread_countperformance_highlightsknowledge_query(project="automation-analytics-backend", persona="developer", section="metadata")— confidencecode_stats(project="automation-analytics-backend")— files_indexed, chunks, search_count
9. Memory
memory_read(key="state/current_work")— follow_ups, active_issues- Discovered work: check memory for discovered work items (created/synced today) if available
10. Output Format
## 📋 Standup Summary
**Date:** YYYY-MM-DD
**Author:** {name}
### ✅ What I Did
**Commits:** {count}
- `{sha}` {message}
**Issues Closed:** {list}
**PRs Reviewed:** {list}
### 🔄 What I'm Working On
- {in-progress issues}
**Open MRs:** {list}
### 📅 Today's Meetings
- {time}: {title}
### 💬 Team Channel (Recent)
- {recent Slack messages}
### 🚧 Blockers
- None (or list)
### 🤖 AI Assistant Status
- **Knowledge Confidence:** {confidence}%
- **Code Index:** {files} files, {chunks} chunks
### 📋 Follow-ups (from memory)
- {priority} {task}
### 📝 Discovered Work (Today)
- **Discovered:** {count} items
- **Synced to Jira:** {count}
- **Issues Created:** {keys}
- **By Type:** {breakdown}11. Post-Standup
memory_session_log("Generated standup summary", "X commits, Y in progress")- On "no such host":
learn_tool_fix("gitlab_mr_list", "no such host", "VPN not connected", "Run vpn_connect()") - On Jira "command timed out":
learn_tool_fix("jira_search", "command timed out", "Jira API timeout", "Check VPN and retry")
Key Details
- Link format:
slack_format→<url|text>, else[text](url); uselinkify_jira_keys/linkify_mr_idspatterns from parsers if available - Jira project: From resolved repo config (e.g. AAP, APPSRE)
- Team channel:
team-automation-analytics(or config override) - Discovered work: From memory/discovered-work if present; suggest
sync_discovered_workfor pending items
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

