Claude Code Github File Scope Checklist: quick fix, steps, and deep guide

Q: Claude Code Github File Scope Checklist

Treat this as a GitHub checklist issue. Confirm the environment, inputs, permissions, logs, and delivery boundary, then use the linked deep guide for the full checklist.

What is the problem?

一份 Claude Code GitHub 文件范围检查清单，帮助新手确认链接类型、分支版本、文件范围、只读边界、敏感信息和客户验收方式。

Quick solution

Treat this as a GitHub checklist 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 guide

Detailed steps

链接类型是什么？文件、目录、PR、issue、commit、分支还是整个仓库。
以哪个版本为准？分支名、commit、tag 或 PR 编号要记录。
要看哪个文件？路径要明确，不要只写“前端文件”。
客户要解决什么问题？语法、构建、样式、接口、逻辑、文案要分清。
是否只读？如果只读，就不要修改、提交或安装依赖。
是否允许小范围修改？允许也要说明修改方式和交付方式。

Commands or code

我可以先做一轮 GitHub 文件范围诊断。请确认：
- 链接对应的文件、分支或 PR
- 希望检查的具体问题
- 是否只读，还是允许小范围修改
- 是否涉及敏感配置、真实数据或生产环境
- 希望怎样验收诊断或修改结果

Risk 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.