ClaudeHack

#slash-commands

4 hacks

  1. 1.
    Parameterize skills with $ARGUMENTS instead of editing prompts(code.claude.com)

    Build slash skills that accept issue numbers, branch names, or formats via $ARGUMENTS / $0 so one command covers many cases.

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
  2. 2.
    Set disable-model-invocation on skills with side effects(arps18.github.io)

    Mark deploy/ship/destructive skills so only an explicit /command runs them—Claude cannot auto-trigger them mid-session.

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
  3. 3.
    Turn recurring prompts into skills you invoke with /name(code.claude.com)

    Save repeatable workflows as SKILL.md (or .claude/commands) so you slash-invoke consistent PR reviews, releases, or checklists.

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·medium·discuss
  4. 4.
    Ask /btw side questions without derailing the main task(support.claude.com)

    Use /btw for single-turn clarifications that share full context but never enter conversation history or burn future tokens.

    0.00 points·14 hours ago·Context Management·easy·discuss