nimbalyst/standup-summary
skills/dev/standup-summary/SKILL.md
Summarize recent git commits in standup format. Use when preparing for standups or summarizing recent work.
$ install --global
skillsauthnpx skillsauth add nimbalyst/skills standup-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 6, 2026, 6:52 AM136.9s1 file scanned
SKILL.md
- name:
- standup-summary
- description:
- Summarize recent git commits in standup format. Use when preparing for standups or summarizing recent work.
Standup Changes Summary
Generate a concise standup-style summary of my recent git commits.
Usage
Arguments: <time-period>
- Examples: 1d (1 day), 2d (2 days), 1w (1 week), 3d (3 days)
Task
- Parse the time period argument (e.g., "1d" = 1 day ago)
- Get git commits since that time using:
git log --since="<time>" --author="$(git config user.name)" --pretty=format:"%h - %s (%cr)" --no-merges - Get the actual commit details using:
git log --since="<time>" --author="$(git config user.name)" --pretty=format:"%h|%s|%b" --no-merges - Summarize the changes in standup format:
- Start with "Here's what I worked on in the last [period]:"
- Group related changes together
- Use concise bullet points
- Focus on what was accomplished (features, fixes, improvements)
- Mention any notable refactoring or infrastructure work
- Keep it brief and conversational (standup style, not formal)
- Don't just list commits - synthesize them into achievements
Output Format
Here's what I worked on in the last [period]:
- [Achievement/feature area]: [summary of what was done]
- [Another area]: [summary]
- [Additional work]: [summary]
Important
- If no commits found, say "No commits found in the last [period]"
- Focus on the "what" and "why", not technical implementation details
- Group similar commits together (e.g., multiple bug fixes, related features)
- Keep it conversational and brief - this is for standup, not a detailed report
Related Skills
nimbalyst/user-research-doc
testing
VerifiedTrustedCommunity
Structure user research findings and insights. Use when documenting user research, interview synthesis, or usability testing results.
20SKILL.mdUpdated Jun 6, 2026
nimbalyst/deep-researcher
testing
VerifiedTrustedCommunity
Parallel multi-agent research with citations. Use when conducting deep research, competitive analysis, or investigating complex topics.
20SKILL.mdUpdated Jun 6, 2026
nimbalyst/customer-interview-sim
testing
VerifiedTrustedCommunity
Simulate customer interviews for practice. Use when preparing for user interviews or testing interview scripts.
20SKILL.mdUpdated Jun 6, 2026
nimbalyst/competitive-analyst
research
VerifiedTrustedCommunity
Competitive analysis with SWOT and feature comparisons. Use when analyzing competitors, comparing products, or evaluating market positioning.
20SKILL.mdUpdated Jun 6, 2026