Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .claude/skills/analyze-issue/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,8 @@ gh issue view <issue_number> --repo ZhuLinsen/daily_stock_analysis --comments

<建议修复、澄清或关闭方式>

若建议后续创建 PR,给出的 PR title 建议符合 `AGENTS.md`:使用 `<类型>: <修改内容>`,不添加 `[codex]`、`codex`、`autocode`、`copilot` 或其他工具/agent 来源前缀;该约定仅用于协作一致性提醒,不应单独作为 review process blocker。

## Risks And Rollback

- 风险点:
Expand Down
10 changes: 9 additions & 1 deletion .claude/skills/analyze-pr/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,14 @@ gh pr diff <pr_number> --repo ZhuLinsen/daily_stock_analysis
gh run view <run_id> --log-failed
```

### Step 2: 按仓库模板检查描述完整性
### Step 2: 检查标题与描述完整性

先检查 PR title 是否符合 `AGENTS.md` 的非阻断建议:

- 格式应为 `<类型>: <修改内容>`,例如 `fix: 修复大盘分析历史记录丢失`
- 类型优先为 `fix`/`feat`/`refactor`/`docs`/`chore`/`test`/`ci`
- 不应包含 `[codex]`、`codex`、`autocode`、`copilot` 或其他工具/agent 来源前缀
- 标题应描述实际变更;若标题与 diff 不符,在描述完整性中指出,但不应单独作为 review process blocker。

对照 `.github/PULL_REQUEST_TEMPLATE.md`,确认是否覆盖:

Expand Down Expand Up @@ -91,6 +98,7 @@ gh run view <run_id> --log-failed
- 必要性:
- 是否有对应 issue:
- PR 类型:
- PR title:
- description 完整性:
- 验证情况:
- 主要风险:
Expand Down
7 changes: 7 additions & 0 deletions .claude/skills/fix-issue/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,13 @@

### Step 6: 需要确认的后续动作

如用户要求创建 PR、生成 PR 标题或整理 PR 描述,PR title 建议遵循 `AGENTS.md`:

- 使用 `<类型>: <修改内容>` 格式,例如 `fix: 修复大盘分析历史记录丢失`
- 类型优先使用 `fix`/`feat`/`refactor`/`docs`/`chore`/`test`/`ci`
- 标题只描述实际改动,建议不添加 `[codex]`、`codex`、`autocode`、`copilot` 或其他工具/agent 来源前缀
- 该约定仅用于协作一致性,不应被单独当作 process blocker

只有在用户明确确认后,才执行:

- 建分支
Expand Down
1 change: 1 addition & 0 deletions .github/copilot-instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ If any instruction in this file conflicts with `AGENTS.md`, follow `AGENTS.md`.
- Desktop: `apps/dsa-desktop/`
- Deployment/workflows: `scripts/`, `.github/workflows/`, `docker/`
- Do not run `git commit`, `git tag`, or `git push` without explicit user confirmation.
- PR titles should use `<type>: <change summary>` such as `fix: 修复大盘分析历史记录丢失`; use `fix`/`feat`/`refactor`/`docs`/`chore`/`test`/`ci` where possible, and avoid `[codex]`, `codex`, `autocode`, `copilot`, or other tool/agent source prefixes. Treat this as process guidance and do not use title format mismatches as a hard review blocker.
- Do not hardcode secrets, accounts, ports, model names, absolute environment-specific paths, or environment-specific branches.
- Reuse existing modules, configuration entrypoints, scripts, and tests instead of adding parallel implementations.
- For user-visible behavior changes, CLI/API changes, deployment changes, notification changes, or report-structure changes, update the relevant docs and `docs/CHANGELOG.md`.
Expand Down
1 change: 1 addition & 0 deletions .github/instructions/governance.instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,5 @@ applyTo: "README.md,docs/**,AGENTS.md,CLAUDE.md,.github/**,.claude/skills/**,scr
- Keep `README.md` limited to homepage-level content such as positioning, high-level capabilities, quick start, main entrypoints, and sponsorship/cooperation; put detailed behavior, configuration, troubleshooting, field contracts, and edge cases in `docs/*.md`.
- Avoid widening permissions, secret exposure, or destructive automation without a clearly documented need.
- Preserve the repository's opt-in auto-tag behavior (`#patch`, `#minor`, `#major`) unless the change explicitly updates release policy.
- When creating, reviewing, or suggesting PRs, prefer PR titles in `<type>: <change summary>` form and omit tool/agent source prefixes such as `[codex]`, `codex`, `autocode`, or `copilot`; treat this as non-blocking guidance, not a review hard blocker.
- If only one language version of a document is updated, explain why the counterpart was not synchronized.
15 changes: 11 additions & 4 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,12 @@
- 变更中英双语文档之一时,需评估另一份是否需要同步;若未同步,交付说明里要写明原因。
- 注释、docstring、日志文案以清晰准确为准,不强制要求英文,但应与文件语境保持一致。

## 1.1 PR 标题规范(非阻断建议)

- 推荐使用 `<类型>: <修改内容>` 作为 PR 标题,例如 `fix: 修复大盘分析历史记录丢失`,优先类型为 `fix`/`feat`/`refactor`/`docs`/`chore`/`test`/`ci`。
- 标题应描述实际变更内容,建议不添加 `[codex]`、`codex`、`autocode`、`copilot` 或其他工具/agent 来源前缀。
- 该规范仅用于协作可读性与一致性提示,不应单独作为 review process blocker。

## 2. AI 协作资产治理

- `AGENTS.md` 是仓库内 AI 协作规则的唯一真源。
Expand Down Expand Up @@ -219,10 +225,11 @@ gh run view <run_id> --log-failed
- PR 审查默认顺序:
1. 必要性
2. 关联性
3. 描述完整性(对照 `.github/PULL_REQUEST_TEMPLATE.md`)
4. 验证证据
5. 实现正确性
6. 合入判定
3. 标题建议(`<类型>: <修改内容>`,且不含工具/agent 前缀;不作为硬性阻断项)
4. 描述完整性(对照 `.github/PULL_REQUEST_TEMPLATE.md`)
5. 验证证据
6. 实现正确性
7. 合入判定
- 对 `fix` 类 PR,必须说明:原问题、根因、修复点、回归风险。
- 合入阻断条件:
- 正确性或安全性问题
Expand Down
Loading