Loading...
Loading...
Found 47 Skills
Get git records for specified users and days, perform code review for each commit, and generate detailed code review reports
Use when creating "changelog", "release notes", "version updates", generating "CHANGELOG.md", or asking about "git history to changelog", "commit summary", "what changed since last release"
Use when generating performance hypotheses backed by git history and code evidence.
Generate daily standup reports from git history, PRs, and a persistent work log. Use when the user says "daily", "standup", "what did I do yesterday", "generate my daily", "daily sync", or asks for a summary of recent work.
Project status report generation from git history, task context, and milestone tracking. Use when creating weekly updates, sprint reviews, stakeholder reports, or project dashboards.
Turn git commits and diffs since an exact start date into a copy-pastable, non-technical client report grouped by feature. Use when the user wants a client update, accomplishment summary, weekly progress note, stakeholder recap, or high-level status report based on git history. Trigger on: client report from commits, summarize git diff since a date, weekly update from git log, non-technical accomplishments, stakeholder-ready changelog. Do NOT trigger for technical release notes, code review, or any request where the date is still ambiguous.
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
This skill should be used when the user asks to "update my README", "refresh the README", "README is outdated", "sync README with the codebase", "improve my README", "keep README up to date", "fix the README", "my README is stale", "update the readme file", "README needs updating", "update readme from git history", or "readme is out of date".
Generate and manage changelogs from git history. Use for release notes, tracking breaking changes, and maintaining project history.
Quick repo state and history scan.
⚠️ MANDATORY - YOU MUST invoke this skill at the start of EVERY task. Reviews git history, status, and context before starting any work. Runs parallel git commands to understand current state, recent changes, and related work. NEVER gather git context manually.