What is the problem?
新手记 GitHub 常用命令时，不要背一长串，而要按场景记：查看状态、拉取更新、暂存、提交、推送、查看差异和处理冲突。本文给出安全练习顺序和项目前注意事项。
Quick solution
Treat this as a GitHub tutorial issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.
Read the deep guideDetailed steps
- Confirm the scenario, tool version, account permissions, inputs, and expected output before changing anything.
- Check configuration, logs, command output, and human review boundaries against the linked deep guide.
- Record the before and after result, then verify that the fix did not introduce platform, privacy, or delivery risk.
Commands or code
git status
git diff
git add README.md
git commit -m "Update README"
git pushRisk notes
Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.