Convert a markdown document (plan, design doc, alignment doc, review notes) into a rich, standalone HTML file with embedded CSS — light theme, system fonts, card-based sections, GitHub-ish color palette. Inspired by the Claude blog post on the unreasonable effectiveness of HTML. The goal is a self-contained .html the…
Generate a privacy-safe version of the current technical problem, safe to paste into external tools. Strips company names, project names, class names, URLs, and internal terminology while preserving the technical substance. Use when you need to search externally without leaking proprietary details.
Generate BDD Gherkin feature files from requirements — even vague ones. Asks clarifying questions to surface edge cases and acceptance criteria, then produces Given/When/Then scenarios. Use when asked for BDD requirements, Gherkin scenarios, .feature files, or acceptance criteria.
Stage, commit, push, and open a pull request in one workflow. Confirms commit message, PR title, and description before acting. Use when the user says "commit push and PR", "push and raise a PR", or invokes /commit-push-pr.
Stage, commit, and push changes. Analyzes the diff, generates a Conventional Commits message, confirms with the user, then pushes. Use when the user says "commit and push", "push my changes", or invokes /commit-push.
Check code changes against project conventions. Accepts a PR number or file paths/globs. Discovers conventions from the codebase itself and reports violations in naming, patterns, and file organization. Use when asked to "check conventions", "review code style", "audit patterns", or "validate naming".
Generate a complete CRUD endpoint for a new resource. Auto-detects project structure (routes, models, test framework) and adapts to Express, Fastify, Flask, and similar frameworks. Use when asked to generate or scaffold a new API endpoint.
Suggest a Conventional Commits message based on current staged and unstaged changes. Does not commit — just outputs the message to copy. Extracts ticket ID from branch name if present. Use when you want a commit message suggestion without committing.
Generate a comprehensive QA testing guide for a pull request. Analyzes the PR diff, researches codebase impact, and produces a structured test plan for QA testers. Use when asked to create a QA guide or test plan for a PR.
Ship staged changes — runs a conventions check, generates a commit message with ticket ID from branch name, commits, and pushes. Use when the user says "ship it", "commit and push", or "send it".
Markdown-only alignment skill. Two-phase collaborative session — probe foundational knowledge first, then walk claims one by one until the user explicitly signals alignment. All output is plain .md. Invoke with /work-towards-alignment-simple .
Run a collaborative session that actively works toward user–Claude alignment on a plan, design, or PR review. Bidirectional and user-paced — Claude first probes the user's foundational knowledge in chat (teaching where needed), THEN writes the alignment doc reflecting what was learned, THEN walks through each claim…