Claude Codeの/ (スラッシュ)コマンドを全部試したので解説する

{
  "permissions": {
    "allow": [
      "Bash(ls:*)",
      "Bash(npm init:*)",
      "Bash(npm install:*)",
      "Bash(mkdir:*)",
      "Bash(npm start)",
      "Bash(npm run dev:*)",
      "WebFetch(domain:docs.anthropic.com)",
      "Bash(git init:*)",
      "Bash(git add:*)",
      "Bash(git commit:*)",
      "Bash(gh repo create:*)",
      "Bash(brew:*)",
      "Bash(gh auth:*)",
      "Bash(git push:*)",
      "WebFetch(domain:github.com)",
      "Bash(gh pr view:*)",
      "Bash(gh pr list:*)"
    ],
    "deny": []
  },
  "enableAllProjectMcpServers": false
}

/cost 
  ⎿ With your Claude Max subscription, no need to monitor 
    cost — your subscription includes Claude Code usage

/cost 
  ⎿ Total cost:            $0.0061
    Total duration (API):  2.2s
    Total duration (wall): 42.6s
    Total code changes:    0 lines added, 0 lines removed
    Token usage by model:
        claude-3-5-haiku:  7.5k input, 16 output, 0 cache 
    read, 0 cache write

 ※ Tip: Use /theme to change the color theme
 ✓ npm permissions: OK
 Your installation is healthy and ready for auto-updates.

 You can also install Claude Code locally to avoid npm
 permission issues using the slash command:

   /migrate-installer

 ※ Tip: Press Shift+Enter to send a multi-line message

 Claude Code v1.0.6

 Always review Claude's responses, especially when running
 code. Claude has read access to files in the current
 directory and can run commands and edit files with your
 permission.

 Usage Modes:
 • REPL: claude (interactive session)
 • Non-interactive: claude -p "question"

 Run claude -h for all command line options

 Common Tasks:
 • Ask questions about your codebase > How does foo.py work?
 • Edit files > Update bar.ts to...
 • Fix errors > cargo build
 • Run commands > /help
 • Run bash commands > !ls

 Interactive Mode Commands:
  /allowed-tools - List all currently allowed tools
  /bug - Submit feedback about Claude Code
  /clear - Clear conversation history and free up context
  /compac - Clear conversation history but keep a summary in
         context. Optional: /compact [instructions for
         summarization]
  /config - Open config panel
  /cos - Show the total cost and duration of the current
      session
  /doctor - Checks the health of your Claude Code installation
  /exit - Exit the REPL
  /help - Show help and available commands
  /ide - Manage IDE integrations and show status
  /init - Initialize a new CLAUDE.md file with codebase
       documentation
  /install-github-a - Set up Claude GitHub Actions for a
  p                repository
  /login - Sign in with your Anthropic account
  /logout - Sign out from your Anthropic account
  /mcp - Show MCP server connection status
  /memory - Edit Claude memory files
  /migrate-install - Migrate from global npm installation to
  r               local installation
  /model - Set the AI model for Claude Code
  /pr-comments - Get comments from a GitHub pull request
  /release-notes - View release notes
  /review - Review a pull request
  /status - Show Claude Code status including version, model,
         account, API connectivity, and tool statuses
  /terminal-setu - Install Shift+Enter key binding for
                newlines
  /vim - Toggle between Vim and Normal editing modes

 Learn more at: https://docs.anthropic.com/s/claude-code

npm install -g @anthropic-ai/claude-code

Claude Code Local Installer
This will install Claude Code to ~/.claude/local
instead of using a global npm installation.
Press Enter to continue or Esc to exit

 Claude Code Status v1.0.6

 Working Directory 
  L /Users/workspace/claude/test-1

 IDE Integration • /config
 ✔  Connected to Cursor extension
  L Installed Cursor extension version 1.0.6 (server version: 1.0.5)

 Account • /login
  L Login Method: Claude Max Account
  L Email: dummy@gmail.com

 Memory • /memory
  L project: CLAUDE.md

 Model • /model
  L Default Opus 4 for up to 50% of usage limits, then use Sonnet 4 (currently Opus)

Please analyze and fix the GitHub issue: $ARGUMENTS.

Follow these steps:

1. Use `gh issue view` to get the issue details
2. Understand the problem described in the issue
3. Search the codebase for relevant files
4. Implement the necessary changes to fix the issue
5. Write and run tests to verify the fix
6. Ensure code passes linting and type checking
7. Create a descriptive commit message
8. Push and create a PR

Remember to use the GitHub CLI (`gh`) for all GitHub-related tasks.