Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in

Coding

Skills, workflows, and commands for Claude.
Kits 1 to 4Category: Coding (4)Remove this filterClear all

  • Review your code changes for bugs before you commit by @slashclone

    @slashcloneRun by the SlashClone team

    For developers who want a second pair of eyes before they commit or open a pull request: review your diff for real bugs and risky changes, not style. Ranks the changed files by risk, flags removed auth checks, SQL built from strings, raw HTML, swallowed errors, focused or deleted tests, and leftover debug code, then reads each change in context and reports only findings it can back up, with file, line, why it breaks, and a fix. Never changes your code unless you ask.

    NewTested

  • Audit a codebase for architecture, UX and security by @clone

    @clone

    For founders and tech leads who need to understand or hand off a codebase: runs parallel reviewers over a repo and produces architecture diagrams at every level, a customer experience report graded per persona against the original plan, and a ranked code review with fixes, each rendered as a clean web page.

    New

  • Plan a feature before Claude writes code by @slashclone

    @slashcloneRun by the SlashClone team

    For anyone building with Claude Code who has watched it charge off in the wrong direction: get a one-page plan first, approve it, then build in small checked steps. Claude reads the relevant code, writes the goal, what done looks like, the files to touch, numbered steps each with a check, and the risks and questions, then stops for your yes. It builds one step at a time, runs typecheck and tests after each, ticks the plan, and tells you what changed from it.

    New

  • Write a pull request description from your changes by @slashclone

    @slashcloneRun by the SlashClone team

    For developers who would rather ship than write PR descriptions: turn your branch into a clear pull request description reviewers can act on. Reads the diff and commits, groups the changes by area, and spots what reviewers need to know: migrations, new environment variables, dependency changes, removed exports and pages, UI changes that need screenshots, and linked issues. Asks you only for the why and how to test, then writes the title and description. Opens the PR with gh only if you say so.

    NewTested

Cookie settings

Cookies that keep you signed in and remember these choices are always on. Everything else is off until you turn it on.