mirror of
https://github.com/GeWuYou/GFramework.git
synced 2026-05-08 01:24:31 +08:00
- 修复 FPR 脚本的 Git 解析、--pr 控制流与 branch 到 PR 的 API 解析路径 - 优化 CodeRabbit summary、CTRF 测试结果与 latest head review threads 的 API-first 提取逻辑 - 更新 skill 文档、agent prompt 与 ai-plan 记录,明确最新提交后 review threads 的优先级
AI Plan
ai-plan/ stores AI task recovery artifacts for this repository, but not every file under it has the same sharing rules.
Directory Semantics
public/todos/- Repository-safe recovery documents.
- Use these for durable task state that another contributor or worktree may need to resume safely.
- These files may be committed.
public/traces/- Repository-safe execution traces that record decisions, validation milestones, and the immediate next step.
- These files may be committed.
private/- Worktree-private recovery space.
- Use this for temporary notes, local scratch recovery points, or state that only matters in the current worktree.
- Keep this directory untracked.
Content Rules
- Never write secrets, tokens, credentials, private keys, hostnames, IP addresses, proprietary URLs, or other sensitive data.
- Never write absolute file-system paths, home-directory paths, or machine usernames.
- Use repository-relative paths, branch names, PR numbers, recovery-point IDs, and stable document identifiers instead.
- Keep committed
public/**content concise, handoff-safe, and understandable without machine-local context.
Naming
- Shared recovery documents should describe the task, for example:
public/todos/cqrs-rewrite-migration-tracking.mdpublic/traces/cqrs-rewrite-migration-trace.md
- Worktree-private files should live under a folder named for the current branch or worktree, for example:
private/feat-cqrs-optimization/private/gframework-cqrs/