richardkmichael
UserA collection of skills, subagents, and hooks for Claude Code.
Categories
Indexed Skills (11)
git-interactive
Reorganize and reshape git commit history: interactive rebase, split commits, squash, fixup, reorder commits, amend old commits, add -p, rebase --onto. Use this skill when the user wants to clean up commits, rewrite history, or make commits semantically atomic. Uses the tmux skill for terminal sessions.
handle-ci-failure
TRIGGER immediately — before any manual investigation — whenever the user mentions CI failures: 'CI is failing', 'why is CI red?', 'the build is broken', 'CI failed', a run ID, a GitHub Actions URL, or any question about a failed workflow run. Do not investigate manually first. This skill reads a project-local CI context file (.github/HANDLE_CI_FAILURE.md), diagnoses the failure, matches it to a known pattern, applies the fix, verifies, and commits + pushes. Targets mechanical CI failures — not open-ended debugging.
matlab-docs
Look up MATLAB / MathWorks docs by function name, mathworks.com URL, or local help-HTML path. Use in preference to WebFetch for any mathworks.com URL — WebFetch gets HTTP 403 from the MathWorks WAF; this skill uses curl. Triggers on "matlab docs", "mathworks docs", a pasted mathworks.com docs URL, or any time you need to consult MATLAB documentation.
matlab-profile
Investigate MATLAB performance problems: time hotspots, memory consumption, parallelism, call patterns. Configures the profiler, runs code under instrumentation, analyzes results across multiple passes, and reports findings with automatic before/after comparison. Use this skill when the user says "profile", "matlab profile", "why is this slow", "memory usage", "hotspot", "performance", "where is time going", "bottleneck", or invokes /matlab-profile. Also use when the user asks to optimize MATLAB code and you need to measure before changing.
tmux
Use interactive CLIs (git, python, gdb, etc.) with tmux by sending keystrokes and scraping pane output.
tool-usage
Query the tool-monitor database to look up and analyze Claude tool usage. Use when asked about tool usage statistics, which tools have been used most, recent tool activity, bash commands run, files read or edited, grep patterns searched, session analysis, or any question about how Claude has been using its tools.
create-commit-message
Write a commit message for the currently staged changes, matching the project's conventions. Use when staged changes need a well-formed message -- on its own, or by an agent after it stages a commit. Reads the staged diff; does not stage or commit.
history
Search and read past Claude Code session transcripts. Use to recall what was said or decided in an earlier session, find a prior discussion by topic, recover content from before a context compaction, pull up a specific session by name or ID, or investigate past sessions in detail by filtering on record type, tool, subtype, or field. Searches conversation prose by default; technical records (tool calls, results, system events) are reachable through filters. Typed as `/history [selector] <query>`, and usable by the model to investigate history on its own.
review-pr-companion
Package a code review as a review branch -- small, reviewer-shaped fix commits plus a REVIEW_HANDOFF.md written for the author's coding agent -- pushed for the author to integrate, with no pull request opened. Use when reviewing a pull request or a local branch and you want to hand back working commits and the reasoning behind them, not just inline comments.
refine-plan
Interview me about the plan
learning-quiz
Teach the human operator the concepts in this session
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.