copilot-instructions.md · diff
git:20261119.92f0209 to git:20261121.7cfcf94
8 added, 34 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
# Repository Instructions
- Canonical source: [`AGENTS.md`](../AGENTS.md).
-
- If any instruction in this file conflicts with `AGENTS.md`, follow `AGENTS.md`.
-
- ## Core Rules
-
- - Respect directory boundaries:
- - Backend: `src/`, `data_provider/`, `api/`, `bot/`
- - Web: `apps/dsa-web/`
- - Desktop: `apps/dsa-desktop/`
- - Deployment/workflows: `scripts/`, `.github/workflows/`, `docker/`
- - Do not run `git commit`, `git tag`, or `git push` without explicit user confirmation.
- - Before creating/updating PRs, PR review, or issue analysis, refresh the latest code baseline with `git fetch --all --prune`; if the worktree is clean and the current branch can fast-forward, run `git pull --ff-only`. If local changes, conflicts, missing upstream, or non-fast-forward history make that unsafe, do not stash/reset/overwrite local state; analyze against fetched remote refs or record the baseline gap before proceeding.
- - 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.
- - Update the relevant usage docs for user-visible changes. Give PRs a descriptive title and appropriate labels for generated release notes. Maintainers archive published versions in `docs/CHANGELOG.md` using the command in AGENTS.md §9.
- - For PR reviews use `.claude/skills/analyze-pr/SKILL.md`. Explain each behavior change, its value, the affected user paths, visible Web/Desktop/report changes and the screenshot or alternative evidence reviewed.
- - Use `README.md` only for project positioning, high-level capabilities, quick start, main entrypoints, and sponsorship/cooperation information; avoid updating README unless the change is homepage-level.
- - Put detailed module behavior, page interaction, topic configuration, troubleshooting, field contracts, implementation semantics, and edge cases in the appropriate `docs/*.md` file instead of README.
- - When config semantics change, sync `.env.example` and assess impact on local runs, Docker, GitHub Actions, API, Web, and Desktop.
-
- ## Validation
-
- - Backend changes: prefer `./scripts/ci_gate.sh`; at minimum run `python -m py_compile` on changed Python files and the closest deterministic tests.
- - Web changes: run `cd apps/dsa-web && npm ci && npm run lint && npm run build`.
- - Desktop changes: build web first, then desktop if feasible.
- - Review work should prioritize CI evidence (`gh pr checks`, workflow logs) before re-running local validation.
- - AI governance changes: run `python scripts/check_ai_assets.py`.
+ Canonical source: [`AGENTS.md`](../AGENTS.md). If any instruction here conflicts with `AGENTS.md`, follow `AGENTS.md`.
- ## AI Asset Governance
+ ## Key Pointers
- - `AGENTS.md` is the single source of truth for repository AI collaboration rules.
- - `CLAUDE.md` must remain a symlink to `AGENTS.md`.
- - Use `.github/instructions/*.instructions.md` for path-specific guidance.
- - Current repository collaboration skills live in `.claude/skills/`; keep them aligned with `AGENTS.md`.
+ - Rules, directory boundaries, validation matrix, changelog/README boundaries, and merge blockers live in `AGENTS.md`.
+ - Claude compatibility entry: `CLAUDE.md` -> `AGENTS.md`; `.claude/skills/` contains copies of the repository skills for checkouts that cannot create symlinks.
+ - Repository collaboration skills live in `.agents/skills/` (`analyze-pr`, `analyze-issue`, `fix-issue`); keep them aligned with `AGENTS.md`.
+ - Path-specific guidance lives in `.github/instructions/*.instructions.md`.
+ - Local review artifacts default to chat output (optional local archive in `.reviews/`, gitignored).
+ - After changing AI governance assets, run `python scripts/check_ai_assets.py`.