← all publishers

block65

@block65 source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 1 week ago last updated

1. ▌
   Tidy · block65

   Run the project's code quality pipeline: oxfmt (format), oxlint --fix (lint auto-fix), and typecheck, then fix the trivially correct issues that remain. Use this skill whenever the user says /tidy, asks to clean up lint/format/type errors, mentions oxfmt/oxlint/typecheck, or wants to tidy code before committing. Also use when the user pastes compiler or lint errors and wants them cleaned up mechanically. Supports '/tidy --typecheck-only' when the user only wants types checked. If the user asks for a report only (e.g. '/tidy --report', 'just check', 'what's broken'), run the pipeline but report issues without fixing.
   1 install
2. ▌
   Handover · block65 bundle

   Wrap up the current session into a complete handover prompt a fresh agent can run with, save it to a file, and copy it to the clipboard so the user can /clear and paste. Use this skill whenever the user says "handover", "hand over to a new agent", "let's handover", "prepare a handoff", "wrap this up for a new session", "I'm going to clear", or otherwise wants to continue this work in a fresh context without losing progress, even if they don't use the word "handover". Accepts an optional steering instruction after the trigger (like /compact takes one), e.g. "handover — just the dragon-hatchery work" or "handover, have the next agent start with the potion tests".
   1 install
3. ▌
   Diff Check · block65 bundle

   Rate the comments and check the changed lines in a diff against the recurring failure modes in agent-written code: narration comments, JSDoc used as an internal note, defensive defaults, sentinels, negated state predicates, magic numbers. Use this skill when the user says 'check my comments', 'rate these comments', 'are these comments any good', 'check the diff', 'diff check', 'did I narrate', 'review my changes before I commit', 'check what I just wrote', or asks whether a comment earns its place. Also use it before reporting a change complete, and when the user complains about comment spam, JSDoc blocks on internal code, or comments explaining code that is no longer there. Pass file paths as args to rate the comments already in those files instead of a diff.
   1 install
4. ▌
   Stage Hunk · block65 bundle

   Stage or unstage specific hunks, or individual lines within a hunk, from a changed file in a git repo without interactive prompts. Use this skill whenever you need to partially stage or unstage changes: committing only the bug fix hunk but not the refactor, taking one line out of a block of added lines, or unstaging something that was staged by mistake. Common phrases: 'commit only the X changes', 'stage that hunk', 'stage just that line', 'only the second of those lines', 'don't include the Y part', 'unstage the refactor'. Pass args as: first line = file path, remaining lines = plain-language description of which changes to (un)stage. Example args: "src/foo.ts\nstage only the import changes, leave the function rename".
   1 install
5. ▌
   Test Suite · block65

   Run the full unit/integration test suite (typically vitest) and end-to-end tests (typically Playwright), then auto-fix failures iteratively using subagents. Use this skill when the user says 'run all tests', 'run the test suite', 'run e2e', 'fix all tests', 'get tests green', 'run vitest', 'run playwright', or any variation of running + fixing tests across a monorepo. Supports --env dev (default) and --env staging for the e2e target. Also trigger when the user asks to 'check everything works' or 'make sure nothing is broken'.
   1 install
6. ▌
   Github Issue · block65

   Create and maintain GitHub issues from user reports and screenshots, fast and without over-investigating. CREATE: use when the user says 'log a GitHub issue', 'file a bug', 'raise an issue', 'open an issue', 'log this on GitHub', or pastes/attaches a screenshot of something broken and asks to report it: captures the symptom, works out steps to reproduce where possible, uploads any screenshot/video and embeds it, applies the GitHub issue authoring standard, and files immediately. UPDATE: use when the user says 'update the issue', 'add a comment to #N', 'attach this to the issue', 'edit the issue body', 'relabel', 'close/reopen the issue': adds comments with media, edits the body, upgrades the repro provenance badge, relabels, and closes/reopens. It does NOT root-cause the code or prescribe a fix; that's for triage.
   1 install
7. ▌
   Stage Trivial · block65

   Scan git diffs and stage only the changes that are self-evidently correct and intentional in context: changes a reviewer would have nothing to deliberate on. Covers lint fixes, formatting, typos, dead code, observability, uniform sweeps, AND self-evidently complete additions like new dev-harness pages wired up via import + menu entry + new file, testid sweeps, mount-marker additions, AGENTS.md pointers. Leaves anything requiring reviewer judgment unstaged: API contract changes, secret rotations, schema requirement changes, algorithm changes, config values the reviewer must weigh, code smells. Use this skill when the user says 'stage the obvious stuff', 'stage trivial changes', 'stage the safe diffs', 'cherry-pick the lint fixes', 'stage what's obviously correct', or wants to triage a messy working tree before committing.
   1 install