explaingit

mistraleuh/my-claude-skills

25Audience · developerComplexity · 1/5ActiveLicenseSetup · easy

TLDR

Fifteen slash command skills for Claude Code that give the assistant fixed personas and workflows for ticketing, dev, review, tests, and security audits.

Mindmap

mindmap
  root((my-claude-skills))
    Inputs
      Fuzzy request
      Existing repo
      Bug report
    Outputs
      Ticket markdown
      Code changes
      Audit report
      CONTEXT.md
    Use Cases
      Run full dev loop
      Hunt bug
      Security review
      Map repo
    Tech Stack
      Claude Code
      Markdown
      Slash commands

Things people build with this

USE CASE 1

Run /do to take a fuzzy request through ticket, code, audit, build, and tests in one chain

USE CASE 2

Drop the /security-review skill onto a project to flag injection, auth, and crypto issues

USE CASE 3

Generate a CONTEXT.md repo map for a new codebase with /knowledge

USE CASE 4

Auto-write commit messages and push with /push instead of typing them by hand

Tech stack

Claude CodeMarkdown

Getting it running

Difficulty · easy Time to first run · 5min

Git clone, copy each subfolder into ~/.claude/skills/, then restart Claude Code; no other deps.

MIT lets you use, modify, and redistribute the skills for any purpose as long as you keep the copyright and license text.

In plain English

This is a collection of 15 slash command skills built for Claude Code, the official command line tool from Anthropic. The author groups them into roles: an architect, a bug hunter, a security auditor, a tech writer, a project manager. Each skill gives Claude a persona and a fixed workflow, so the assistant follows steps instead of jumping straight to code. The headline command is /do, which chains five other skills together in one shot. /todo writes a detailed ticket from a fuzzy request. /dev implements the ticket. /verify-dev audits the code line by line against the ticket. /build runs types, lint, and unit tests. /test runs functional tests. If any gate fails, /do loops back to /dev, up to three retries per gate, then either reports green or stops with a clear failure state. Installation is a git clone, then copy each subfolder into ~/.claude/skills/, then restart Claude Code. After that, plain English phrases like 'commit and push' or 'there is a bug on X' route to the right skill automatically. Each skill description lists trigger phrases, so the user does not need to memorize the slash names. The other skills cover quality work and documentation. /hunt reproduces and isolates bugs before claiming a fix. /security-review focuses on injection, auth, crypto, and dependency issues with CWE references. /refactor produces a line by line plan with risk notes. /knowledge generates a CONTEXT.md map of an existing repo, and /doc-update keeps existing docs in sync with code changes. /push writes the commit message and pushes. The author says the skills were built originally for a Next.js, FastAPI, and SQLite stack at his company, but the patterns are meant to be stack neutral. He reports roughly 80% fewer follow-up prompts and review cycles cut in half on production tickets. The license is MIT.

Copy-paste prompts

Prompt 1
Install MisTraleuh's my-claude-skills into ~/.claude/skills and verify /do is registered
Prompt 2
Adapt the /dev skill to a Go and Postgres stack while keeping the ticket gating loop
Prompt 3
Write a new slash skill in this repo's style for running database migrations safely
Prompt 4
Trace how /do retries when /test fails and add a fourth retry with a different prompt
Prompt 5
Port the /knowledge CONTEXT.md generator into a standalone shell script
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.