Menu
SkillsMP has collected 11 skills from egladman/dotfiles-darwin. Open a skill to review its source and details.
Showing 11 of 11 collected skills.
Use when writing a git commit message, or rewording existing unpushed ones, so they match this user's format. Triggers on "commit this", "write the commit message", "fix the commit messages", "reword the commits", "clean up my commit history". The format is…
Use when renaming a Go symbol (a function, method, type, variable, struct field, or package-level identifier) across a module. Triggers on "rename this go function", "rename X to Y in this package", "rename this symbol everywhere", "rename this variable".…
Run every go-review-* skill (style, nit, skeptic, and legibility if applicable) in parallel against a target Go directory and merge the findings. Use when the user wants a full review pass — e.g. "ultra-review @pkg/foo", "run all the go reviews on…
Full review pass on a change or directory, routed by stack. Detects Go vs TypeScript and delegates to go-review-ultra / ts-review-ultra; reviews any other language directly. Also runs a PR-scope check. Use when you want the complete pre-commit/pre-PR review,…
Use when you want a full review pass of TypeScript code. Triggers on "ultra-review src/modules/foo", "run all the ts reviews on this module", "give me everything you've got on this file". Fans out ts-review-style, ts-review-nit, and ts-review-skeptic in…
Use when the user wants a PR scope assessment surfaced directly — "is this PR too big", "how should I split this", "chunk this into PRs", "scope check", or before opening a large PR. Runs the pr-scope-analyzer agent and relays its full output verbatim.
Use when editing prose, technical docs, or READMEs to remove AI writing patterns. Detects and rewrites 42 general patterns plus 7 technical-doc patterns. Based on Wikipedia's "Signs of AI writing" guide.
Convert false-positive Go review findings into structural refactors that lift hidden invariants into the call site's view. Use when the user provides a list of code-review findings already inspected and judged false positives, and wants recommendations for…
Scrutinize Go code for measurable, quantifiable performance wins — even when they sacrifice idiom or legibility. Use when the user asks to "optimize", "ultra-optimize", "make faster", "performance tune", "reduce allocations", "benchmark and improve", or…
Use when you have a list of TypeScript code-review findings already inspected and judged false positives, and want recommendations for how to restructure the code so future reviewers don't misread it. Produces a per-finding refactor sketch plus cross-cutting…
Use when you want to scrutinize TypeScript or Node.js code for measurable, quantifiable performance wins. Triggers on "optimize", "make faster", "reduce allocations", "benchmark and improve", "squeeze cycles", "V8 hot path" in TypeScript/Node code. Requires a…