Here’s the English translation of the provided text:

“cc provides so many commands, which ones are actually useful? I’m going to watch some video tutorials on Douyin and simply record what I find helpful.

The generated normalized git logs automatically include copyright information, but since we’re now using domestic large models, there’s no need to add the copyright (GitHub displays cc as a collaborating developer).

Find the user configuration file and add the setting "includeCoAuthoredBy": false.

/init – Analyze the current folder to generate an overview for better understanding by the large model. /compact /clear – Daily commands, no explanation needed. claude --dangerously-skip-permissions – Use with caution! This is how the null file from the previous draft was created; there are many small issues with cc on Windows. # – Enter memory mode, commonly used at the user level rather than project level. I frequently use this to write common projects into it. /ide – Can perceive the text data currently selected in VS Code, similar to what’s in trae. When interacting frequently, I provide function snippets from related files. Switching to the command line, I haven’t found anything like this functionality—especially with many project files, providing accurate code generation relies on having reference functions. mcp? – Haven’t really tried this type of tool; will explore further if needed. I always find it a bit cumbersome to use.

Custom commands – No demand; the user-level equivalent of the git normalization submission I previously wrote is sufficient.”