📚 Core commands 📋 Command cheat sheet Command icon describes the frequency of use in one sentence /help🆘View the help document⭐⭐⭐⭐⭐ /clear🧹Clear the conversation record⭐⭐⭐⭐⭐ /undo⏪Undo the previous message⭐⭐⭐⭐ /commit💾Git Submission Assistant ⭐⭐⭐⭐⭐ /review👨🏫Code Review⭐⭐⭐⭐ /test🧪Automated Testing⭐⭐⭐ /plugin🧩Plug-in Management⭐⭐⭐⭐ /bashes📊Background Task Monitoring⭐⭐⭐ /squad👥Expert Team⭐⭐ /help - 🆘 Novice Village Tour Guide Image metaphor: like Novice tutorial NPC function in the game: Display all available commands View instructions for use Get help documents Usage scenarios: 👨💻 You: I don’t know which commands can be used... 🤖 Claude: Type /help to see the full list of commands! Scenario: - Just started using Claude Code - Forgot how to use a certain command - Want to see what new features are available Analogy: 📱 "Settings" on the phone → View all features 🎮 "Help" on the game → Understand how to play 🗺️ "Legend" on the map → Know the symbols /clear - 🧹 Clear the chat history Image metaphor: Just like clearing the browser history, giving the brain a "restart" Function: Clear the current conversation history Release context space and restart the conversation. Usage scenarios: 👨💻 Situation 1: Talking too much and not being relevant Off content "I just talked for a long time about how to make videos, and now I want to ask code questions, but Claude is still answering me in the context of the video..." → /clear Reset the conversation! 👨💻 Situation 2: Want to start a new topic "The discussion on the previous project is over, now we want to start a new project" → /clear clears the old conversation! 👨💻 Scenario 3: The conversation is too long and the response is slow "After 500 rounds of chatting, Claude starts to slow down..." → /clear frees up memory! Analogy: 🧠 The brain's "clear cache" → refocus 📝 The whiteboard's "erase and rewrite" → start new content 🎬 The movie's "scene change" → switch scenes ⚠️ Note: Previous conversations cannot be restored after clearing. It is recommended to save important content first /undo - ⏪ Time travel machine Image metaphor: Just like the "read file" function in the game Function: Undo the previous message Return to the previous conversation status and rethink the answer. Usage scenario: 👨💻 Situation 1: Wrong question asked. You: "Delete the database for me" (wait, I want to say backup! ) → /undo Undo! 👨💻 Situation 2: Claude misunderstood Claude: "I deleted all the files for you" You: 😱 That's not what I meant! → /undo rollback! 👨💻 Situation 3: Want to change the way of thinking Claude: (given a plan) You: "This plan is not suitable, I want to change the angle" → /undo Do it again! Analogy: ⏮️ "Back" of the video → go back to the previous 📖 "turn back to the previous page" of the book → re-read 🎮 "SL method" of the game → load the file again 💡 Tips: You can /undo multiple times in a row Similar to Git's reset operation /commit - 💾 Git submission assistant Image metaphor: It's like taking a photo to archive, saving the current working status Function: Automatically analyze code changes Generate submission information and execute git commit Usage scenarios: 👨💻 Situation 1: After writing the code and want to submit it You: "Write a login function for me Yes, I want to commit now" Claude:
- git status (see changes)
- git diff (see specific changes)
- Generate commit information: "feat: implement user login function"
- git commit -m "..." 👨💻 Situation 2: I don’t know what to write commit message You: /commit Claude: "I helped you analyze the changes and suggest writing like this..." 👨💻 Situation 3: Need standardized commit information You: "I want a commit that conforms to team specifications" → /commit automatically generates the standard format! Analogy: 📸 "Photo archive" of photography → record the current status 💾 "Save progress" of the game → storage node 📦 "Packaging" of express delivery → organize and send 💡 Advanced usage: # commit will automatically:
- Analyze which files have been changed
- See the nature of the change (new features/repairs/refactoring)
- Generate a clear commit message
- Ask if you want to push to remote /plugin - 🧩 Plug-in manager Image metaphor: Just like the "App Store" of your mobile phone Function: Install/uninstall plug-ins Manage Skills View available extensions Usage scenarios: 👨💻 Situation 1: Want to install new features You: /plugin install document-skills (just like: App Store → Download Microsoft Office) 👨💻 Situation 2: View installed plug-ins You: /plugin list (Like: Phone settings → View installed apps) 👨💻 Scenario 3: Add plugin market You: /plugin marketplace add anthropics/skills (like: add new app store) Common subcommands: /plugin list # View installed plugins /plugin install [name] # Install plugin /plugin uninstall [name] # Uninstall plugin /plugin marketplace add # Add market Analogy: 📱 iPhone’s App Store → Install apps 🎮 Steam’s game library → Manage games 🔌 Browser’s extension store → Add function 🛠️ Development command /review - 👨🏫 Code review teacher Image metaphor: It's like asking an experienced senior to help you look at the code. Function: Check code quality, discover potential problems, provide optimization suggestions. Usage scenarios: 👨💻 Situation 1: After writing the function, you want others to take a look at it. You: "I just finished writing this function, help me see if there are any problems." Claude: ✅ The code logic is correct ⚠️ The variable naming can be clearer 💡 It is recommended to add error handling 🔒 Note that there may be security issues here 👨💻 Situation 2: Want to confirm before refactoring You: "If you are going to refactor this part of the code, help me evaluate it first" → /review Comprehensive analysis! 👨💻 Situation 3: Prepare to submit a PR You: "I'm about to submit a Pull Request, help me with the final check" → /review code review! Review content: 🐛 Bugs and errors 🎨 Code style ⚡ Performance issues 🔒 Security risks 📚 Document integrity Analogy: 📝 "Teacher's correction" of composition → Find problems 🏗️ "Quality inspection and acceptance" of construction → Ensure quality 🎬 "Preview screening" of movie → Listen to feedback /test - 🧪 Automatic testing laboratory Image metaphor: Just like the "quality inspection" link of a factory. Function: Generate test code, run test cases, check coverage. Usage scenarios: 👨💻 Situation 1: New functions are written and need to be tested. You: " Help me write a test for this function" Claude: - Generate unit tests - Cover various edge cases - Add assertion checks 👨💻 Case 2: Want to know if the code is correct You: /test Claude: "Run 15 tests, all passed! ✅" 👨💻 Situation 3: After discovering a bug You: "I just fixed a bug, help me add a test to prevent recurrence" → /test regression test! Analogy: 🏥 "Various inspections" of physical examination → ensure health 🚗 "Factory inspection" of cars → ensure quality 🍔 "Testing" in restaurants → confirm taste /bashes - 📊 Background task monitoring Image metaphor: Just like Windows' "Task Manager" Function: View commands running in the background Monitor long-term tasks Manage shell processes Usage scenarios: 👨💻 Situation 1: A long-running task You: "I just ran npm install and want to see the progress" → /bashes Check the status! 👨💻 Situation 2: There is a command running in the background You: "I started a server before, and now I want to see if it is still there" → /bashes lists all background tasks! 👨💻 Situation 3: Want to stop a task You: "The compilation task is stuck and want to terminate" → /bashes → Find the ID → Terminate Display information: 📝 Task ID ⏱️ Running time 📊 Current status 📤 Output content Analogy: 💻 Task Manager → View the process 📱 Background application of the phone → Manage the running App 🏭 Factory monitoring screen → real-time status 🎯 Special command /squad - 👥 Summon a team of experts Image metaphor: Just like the Avengers, different experts are summoned according to the task Home Role: Analyze project requirements Form a professional team Multi-role collaboration Usage scenario: 👨💻 Situation: Need to do a complex project You: /squad "Develop an e-commerce website" Claude Analysis: This project requires: - 🎨 UI/UX designer - 💻 Front-end engineer - 🔧 Back-end engineer - 💾 Database expert - 🔒 Security engineer Then form a virtual team with each role providing expert advice! Analogy: 🎬 The "crew" of a movie → director + actor + photographer... 🏗️ The "engineering team" of a building → designers + workers + electricians... ⚽ The "lineup" of football → forward + midfielder + defender... 🎮 Practical drill Scene 1: Start a new project #
- Clear the previous dialogue /clear #
- Start discussing the new project "I want to make an AI information aggregation station" #
- Need to form a team /squad "AI Information Aggregation Station" #
- Submit the code after writing /commit #
- Review /review before submitting Scenario 2: Debugging issues #
- Found a problem with the code "This code reported an error" #
- Let Claude review /review #
- After repairing, I want to undo the previous wrong attempt /undo #
- Add a test to prevent recurrence /test #
- Submit the repair /commit Scenario 3: Install new features #
- View available plug-ins /plugin list #
- Install the required plug-ins /plugin install frontend-design #
- Use the newly installed plug-in "Create a page using frontend-design skill" #4. Uninstall if no longer needed /plugin uninstall frontend-design 💡 Usage tips 🎯 Combination skills Tip 1: Code submission trilogy
- /review # Review the code first
- /test # Run the test
- /commit # Submit after confirming that it is correct Tip 2: Start over
- /undo # Undo the error
- /clear # Clear the conversation
- Re-question # Change your mind Tip 3: Plug-in management
- /plugin list # See what is there
- /plugin install [name] # Install what you need
- Use skill # to start working
- /plugin uninstall # Uninstall after use ⚡ Shortcut key thinking Think of commands as shortcut keys: Command analogy shortcut key memory method /clear Ctrl+L to clear the screen /undo Ctrl+Z to undo the operation /commit Ctrl+S to save the file /help F1 help document 🚫 Common misunderstandings ❌ Wrong usage Misunderstanding 1: Overuse /clear ❌ /clear for every question (lost the context, Claude) Unable to understand continuous conversations) ✅ /clear only when switching topics Misunderstanding 2: /commit without looking at it ❌ /commit directly after writing the code (possibly mention Submit the problematic code) ✅ /review → /test → /commit Misunderstanding 3: Forgot that /undo can be used continuously ❌ If you make a mistake, /clear and start over (losing useful conversation history) ✅ Continuous /undo to return to the correct position 📚 Learning path Novice stage ✅ /help - Read the help document first ✅ /clear - Learn to clear conversations ✅ /undo - Learn to undo operations Advanced stage ✅ /commit - Start using Git workflow ✅ /plugin - Install and manage plug-ins ✅ /review - Develop code review habits Advanced stage ✅ /test - Automated testing ✅ /bashes - Background task management ✅ /squad - Complex project collaboration 🎓 Memory tips: find help for help documents, clear for clearing dialogues, undo for undoing operations, code submission commit, code review, test for automatic testing, plug-in management plugin, background task bashes. The expert team squad is summoned, and the combination is highly efficient! 🔗 Extended reading Official documentation: https://docs.claude.com/claude-code Video tutorial: YouTube Search "Claude Code Tutorial" Commands are just tools, the key is to understand their functions and usage scenarios! Using these commands proficiently will increase your development efficiency by 10 times! 🚀