Use this skill to perform a thorough logic inspection and sanity check on source code to catch common oversights such as off-by-one errors, missing safety/null checks, resource leaks, edge-case failures, type overflow/underflow, and unhandled error returns.
Use this skill to "provide a code skeleton" for a class, group of functions, or other small-to-mid-sized collection of source code when the purpose of that code has been sufficiently determined.
Use this skill to deconstruct legacy, prototype, or dense code into a concise, high-level, declarative description. Relieves the developer of reading, abstracting, and documenting legacy mechanics so they can focus immediately on organic, maintainable reimplementation.
Use this skill when the user wants a "coworker presence" during the workday, i.e. a warm, directive companion that keeps them on track with their Jira tickets, remembers where they left off, and helps them get started and resume after interruptions. Not for domain or coding questions.
Use this skill when asked to check, or add, the use of logging functionality to a piece of code.
Cheatsheet for future sessions working on the gim codebase. Covers architecture, established error-handling patterns, known gotchas (Unicode quotes, pull-context detection), and a backlog of remaining improvements discovered during the September 2026 error-handling pass.
Use this skill to audit a tool with regard to its workflow, i.e. running use cases and identifying shortcomings in functionality, edge-case handling, and user experience.