.claude/skills/git-brag/SKILL.md
Find all commits made by the current git user that touched a given path, formatted for a brag/perf-review doc
npx skillsauth add guidodinello/claude-dotfiles git-bragInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Find commits you authored that touched specific files or folders. Useful for perf reviews, brag docs, or auditing your contributions to documentation.
The user may optionally specify a path or glob (e.g. /git-brag .github/instructions/). If no path is given, default to .github/instructions/.
Run these two commands in parallel:
git config user.name && git config user.email
Use the returned name as the --author filter. Use the user-supplied path (or .github/instructions/ as default).
git log --author="<name>" --format="%H %ai %s" -- "<path>"
For each commit hash returned, run in parallel:
git diff-tree --no-commit-id -r --name-only <hash>
Filter the output to only lines that start with the searched path, so you show only the relevant files changed per commit (the commit may have touched other files too).
Present results as a clean markdown list ready to paste into a perf review doc:
Found N commits touching `<path>`:
- **[TICKET] Commit subject** (`shortHash`) — YYYY-MM-DD
- `path/to/file.md`
- `path/to/other.md`
If no commits are found, say so clearly and suggest broadening the path.
After listing results, offer to:
git show <hash> -- <path>)--after / --beforedevelopment
Writes React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.
development
Show a Claude Code usage report — model token breakdown, estimated costs, top projects, and session patterns. Delegates to the stats-analyzer subagent (Haiku) to avoid polluting the main context with raw data.
development
Use this skill whenever the user wants to write, refine, or break down a subtask for a software ticket — especially backend endpoints, frontend components, or API integrations. Trigger when the user shares a user story, acceptance criteria, or ticket scope and asks for a subtask, refinement card, or implementation breakdown. Also trigger when the user says things like "help me refine this", "write a subtask for X", "break this down", or "create a card for the endpoint / component / feature". This skill produces structured, audience-appropriate subtask write-ups for developers, PMs, and QAs alike.
development
Run the full quality pipeline (type-check, linting, tests) via the quality-checker subagent. Returns a concise summary of issues without flooding the main context with raw output.