ryanalexanderbrashear
- 10 skills
- 0 followers
- 8 hours ago last updated
- ▌ Commit · ryanalexanderbrashearWrite a commit message for the staged changes — subject in the repo's title format, body explaining why — and commit it non-interactively. Also advises on which commits should exist by the time a PR merges. Use when the user asks to commit, wants a commit message written or improved, or asks how to tidy a branch's commits before merge.
- ▌ Grill Me · ryanalexanderbrashearInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- ▌ Create Pr · ryanalexanderbrashearOpen a pull or merge request for the current branch on GitHub, GitLab, Bitbucket, or Azure DevOps, with the title and description filled in from the branch's own commits using the standard PR template. Use when the user wants to open, create, raise, or draft a PR or MR for the work on the current branch.
- ▌ Plan Work · ryanalexanderbrashearInvestigate a bug or feature from a ticket or a user's description, then write an implementation plan to a file for the user to review and iterate on before any code is written. Use when the user wants a plan, wants work scoped or broken down, asks how they would approach a ticket, or hands over a ticket ID, ticket URL, or bug report.
- ▌ Triage CI · ryanalexanderbrashearDiagnose a failing CI run — find what actually failed, and say whether it is a real failure, an environment difference, or a suspected flake, with the evidence. Read-only; it does not fix anything. Use when a CI run or PR check is red, when the user asks why a build failed, or whether a failure is a flake.
- ▌ File Issue · ryanalexanderbrashearFiles a bug report or work item in the project's tracker — GitHub, GitLab, JIRA, Linear or whatever the repo actually uses — with the report in the reporter's words, the cause traced or explicitly unknown, and a reproduction. Use when the user reports a bug, says "file this", "open a ticket", "raise an issue", or when work is discovered that will not be done now and would otherwise be lost.
- ▌ Split Work · ryanalexanderbrashearSeparate tangled work into coherent commits or branches — uncommitted changes into several commits, one commit into several, or one branch into two — with a rescue point recorded first and the result verified content-identical to the original. Use when the user wants to split a branch, split or separate commits, pull one change out of a mixed batch, or move work onto its own branch.
- ▌ Plan Project · ryanalexanderbrashearTurn a description of a project's end goal into a project plan — success criteria, milestones, and a numbered work breakdown that plan-work can pick up item by item. Covers both a new codebase built from nothing and a large body of work inside an existing one. Use when the user describes something they want to build or change at the scale of weeks rather than hours, wants to start a new app, service, tool, or library from scratch, asks for a roadmap, wants an epic or initiative broken down, or asks how to approach a project.
- ▌ Address Review · ryanalexanderbrashearRead the outstanding review feedback on a pull request, triage it, apply the fixes, and reply on each thread saying what happened. Use when the user wants to address, respond to, handle, or work through PR review comments or reviewer feedback, or asks what a reviewer is still waiting on.
- ▌ Regression Test · ryanalexanderbrashearWrite a test that pins a bug so it cannot come back — and prove it fails against the broken code before accepting it. Use when a bug has been found or fixed and should be guarded, when the user asks for a regression test or asks whether a fix is covered, or when a defect keeps recurring.