RileyCornelius
- 7 skills
- 0 followers
- 6 hours ago last updated
- ▌ Git Commit · rileycorneliusGenerate well-structured git commit messages with a standard subject line and optional description. Use when committing staged changes, writing commit messages, or when the user asks to commit.
- ▌ Git Worktrees · rileycornelius bundleCreate or manage isolated git worktrees for parallel feature work, experiments, reviews, or bug fixes without disturbing the current checkout. Use when the user wants a separate workspace or branch, asks to isolate work before implementation, or when working in the current tree risks conflicts or mixing unrelated changes.
- ▌ Code Debugging · rileycornelius bundleInvestigate bugs, failing tests, broken builds, performance regressions, and unexpected behavior by finding root cause before fixing. Use when something is failing or unclear, especially after unsuccessful fix attempts or when the cause is not yet proven.
- ▌ Code Reviewing · rileycorneliusReview code changes for correctness, regressions, security, maintainability, test coverage, and production readiness. Use when asked to review a PR, audit a diff, look for bugs or risks, assess merge readiness, or do a final pass after a substantial implementation.
- ▌ Code Simplifier · rileycorneliusSimplify recently changed code for clarity, consistency, and maintainability without changing behavior. Use when the user wants a cleanup, refactor, polish pass, or readability improvement on code that already works and should keep the same functionality.
- ▌ Code Brainstorming · rileycorneliusTurn coding ideas into approved designs and planning-ready implementation briefs before coding starts. Use for new features, meaningful behavior changes, ambiguous implementation requests, refactors that change system shape, or early architecture and design discussions. Do not use for tiny obvious edits, isolated typo fixes, trivial null checks, or other straightforward bug fixes that do not need design work.
- ▌ Code Explain Visually · rileycorneliusExplain code with diagrams, analogies, and step-by-step walkthroughs. Use when the user wants help understanding a function, file, module, request flow, architecture slice, or unfamiliar codebase area, especially when a visual explanation would make the behavior easier to follow.