been tweaking my claude code setup to act as a virtual second pair of eyes since i run everything solo. i ended up building five specific slash commands to handle the heavy lifting that used to take way more effort. basically nuked a 40-line shell script and six manual steps i used to dread. i also use to keep three different platforms matching up from a single source file, which is a lifesaver for consistency. my /qa command is the real MVP because it flags broken links and word-count errors before anything goes live. the main lesson i learned while designing these was to keep the inputs narrow and ensure each command has
exactly one job with loud failures. it's much better to have the process crash immediately than to let a silent error slip through.
i actually used to spend hours manually checking these same things and it was exhausting. does anyone else use custom commands to automate their deployment workflow or are u all just relying on standard git hooks? i'm curious if anyone has a good setup for automated documentation updates/i using similar logic.
full read:
https://dev.to/raxxostudios/5-claude-code-slash-commands-i-built-and-use-daily-814