50 reviewed skills.
Requires real evidence before a software change is reported as finished: build and tests run, the change exercised directly, at least one edge case tried, and results shown. Use when you implement, fix or verify code and can run checks.
Use when you have just written or changed code and before presenting it: runs a focused second pass for the mistakes generated code commonly contains, fixes what it can, and reports what was fixed and what needs the author's attention.
Use when you are about to commit a non-trivial technical or business decision, claim something is safe or correct, or change something hard to undo. Runs a short, bounded adversarial review of the decision before it stands.
Expands a fuzzy one-line request into a short brief covering audience, deliverable, timing, setting, purpose, method, scale, and length, with guesses marked. Use when a request could reasonably be read several ways.
Standing approach for reviewing code: rank findings by impact, explain why, and suggest a fix. Use when asked to review code, a change or a pull request.
Standing instructions for helping someone think through a personal situation by reflecting back and asking open questions, not advising. Use when someone wants to think out loud or journal.
Reviews a draft email to a client for clarity, tone, promises and risks (scope, dates, prices) and returns a tightened version with the changes explained. Use when someone at an agency shares a draft client email or asks to check a client message before sending.
Drafts quick, warm replies to everyday customer messages such as booking requests, price questions, complaints and thank-yous, in a small business owner's own voice. Use when messages pile up in your inbox, chat or social accounts.
Builds a day-by-day onboarding checklist for your first employee, covering paperwork, training and a warm start. Use when you are about to hire your first person and want nothing forgotten.
Gives the steps and wording for answering a late cancellation or a missed appointment calmly, fairly and with a way to rebook. Use when a customer cancels late or does not turn up.
Guides a manager through a tricky people situation (low engagement, conflict, a struggling team member) with questions, options and a next step, rather than a lecture. Use when a team lead asks how to handle something with a person on their team.
Helps you turn your work experience into short, structured interview stories you can reuse for many questions, then practise them. Use when you have interviews coming up and freeze on 'tell me about a time when...'.
