@fitlab-ai/agent-infra 0.3.2 → 0.4.1

package/templates/.agents/skills/commit/SKILL.md

@@ -1,139 +1,40 @@
 ---
 name: commit
-description: >
-  Commit current changes to Git, including copyright header year
-  check and task status update. Triggered when the user requests
-  a code commit or save changes.
+description: "Commit the current changes to Git"
 ---
 
 # Commit Changes
 
-Commit current changes to Git.
+Create a Git commit without overwriting user work and update the related task state when needed.
 
-## Step 0: Check Local Modifications (CRITICAL)
+## 1. Check Local Modifications (CRITICAL)
 
-**Mandatory**: Before any edits, you **must** check the user's local modifications to avoid overwriting their work.
+Before any edit, inspect:
 
 ```bash
 git status --short
 git diff
 ```
 
-**Rules**:
-1. **Read `git diff` output carefully** - understand what the user has already changed
-2. **Make incremental edits** on top of user modifications - do not overwrite their implementation
-3. **If your planned edits conflict** with user modifications, ask the user first:
-   ```
-   This file has local modifications:
-   - Your changes: [describe user's changes]
-   - My planned changes: [describe planned changes]
-   Please confirm how to proceed.
-   ```
-4. **Do NOT** rewrite code the user has already implemented
-5. **Do NOT** add "improvements" the user didn't ask for
+Respect existing user changes. If your planned edit conflicts with them, stop and ask before proceeding.
 
-## Step 1: Update Copyright Header Years (CRITICAL)
+## 2. Update Copyright Headers
 
-**Mandatory**: Before committing, check and update copyright headers in all modified files.
+Use the current year dynamically and only update files that are already modified.
 
-### Get Current Year
+> The full copyright workflow lives in `reference/copyright-check.md`. Read `reference/copyright-check.md` before editing any header.
 
-```bash
-date +%Y
-```
-
-**Never hardcode the year.**
-
-### Check Modified Files
-
-```bash
-git status --short
-```
-
-### For Each Modified File
-
-Check if the file has a copyright header:
-```bash
-grep "Copyright.*[0-9]\{4\}" <modified_file>
-```
-
-If it has a copyright header and the year is not current, update the year.
-
-**Common formats**:
-- `Copyright (C) 2024-2025` -> `Copyright (C) 2024-{CURRENT_YEAR}`
-- `Copyright (C) 2024` -> `Copyright (C) 2024-{CURRENT_YEAR}`
-- `Copyright (C) 2025` -> `Copyright (C) {CURRENT_YEAR}` (if already current)
-
-### Copyright Checklist
-
-Before executing `git commit`:
-- [ ] Used `date +%Y` to dynamically get the current year
-- [ ] Checked all files about to be committed
-- [ ] Updated copyright year in all files that have copyright headers
-- [ ] **Never** hardcoded the year
-- [ ] **Only** updated modified files, not the entire project
-
-## Step 2: Analyze Changes and Generate Commit Message
-
-```bash
-git status
-git diff
-git log --oneline -5
-```
-
-Generate commit message in Conventional Commits format:
-- `<type>(<scope>): <subject>` (English imperative mood, max 50 chars)
-- Body: 2-4 bullet points explaining what and why
-- Signature block:
-  - `Co-Authored-By: {Your Model Name} <noreply@provider.com>`
-  - If task-related, append extra `Co-Authored-By` lines for other contributing agents
-
-### Multi-Agent Co-Authorship (If Task-Related)
-
-If the commit belongs to an active task and `.agent-workspace/active/{task-id}/task.md` exists:
-
-1. Read the `## Activity Log` section from `task.md`.
-2. Extract all unique agent names from entries matching `by {agent}`. A loose pattern such as `by (\S+)` is acceptable.
-3. Exclude `human` because the Git author is already the human user.
-4. Map each agent to a `Co-Authored-By` line:
-
-| Agent | Signature |
-|-------|-----------|
-| `claude` | `Co-Authored-By: Claude <noreply@anthropic.com>` |
-| `codex` | `Co-Authored-By: Codex <noreply@openai.com>` |
-| `gemini` | `Co-Authored-By: Gemini <noreply@google.com>` |
-| `opencode` | `Co-Authored-By: OpenCode <noreply@opencode.ai>` |
-
-5. Build the signature block with these rules:
-   - Keep the current executing agent's signature in its original position.
-   - Append other unique participating agents as additional `Co-Authored-By` lines.
-   - Do not duplicate the current agent if it already appears in `Activity Log`.
-   - For unknown agent names, use `Co-Authored-By: {Agent} <noreply@unknown>`.
-
-If the commit is not task-related, keep the existing single-signature behavior.
-
-## Step 3: Create Commit
+## 3. Build the Commit Message
 
-```bash
-git add <specific-files>
-git commit -m "$(cat <<'EOF'
-<type>(<scope>): <subject>
+Review status, diff, and recent history, then prepare a Conventional Commit with the correct co-author lines.
 
-- <bullet point 1>
-- <bullet point 2>
+> Commit message rules, examples, and multi-agent co-authorship details live in `reference/commit-message.md`. Read `reference/commit-message.md` before writing the commit.
 
-Co-Authored-By: {Your Model Name} <noreply@provider.com>
-<additional Co-Authored-By lines for other task participants, if any>
-EOF
-)"
-```
+## 4. Create the Commit
 
-**Important**:
-- Add specific files by name - do NOT use `git add -A` or `git add .`
-- Do NOT commit files that may contain secrets (.env, credentials, keys)
-- For task-related commits, keep the current agent first and append the extra lines generated above
+Stage specific files only and run `git commit` with the prepared message.
 
-## Step 4: Update Task Status (If Task-Related)
+## 5. Update Task Status When Applicable
 
 Get the current time:
 
@@ -141,93 +42,20 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-After committing, update task status based on the situation:
-
-For all cases below, **append** to `## Activity Log` in task.md (do NOT overwrite previous entries):
-```
-- {yyyy-MM-dd HH:mm:ss} — **Commit** by {agent} — {commit hash short} {commit subject}
-```
-
-> **⚠️ Situation Check — you must inspect task state first, then choose exactly one matching case below:**
->
-> - Check `task.md` for `current_step`, workflow progress, and the latest `## Activity Log` entry
-> - Check whether the latest `review.md` / `review-r{N}.md` exists and whether the latest review passed with no issues
-> - Check whether any follow-up repair, review, or PR creation step is still pending
->
-> | Decision basis | Required case |
-> |---------------|---------------|
-> | All workflow steps complete + latest review passed with no issues + all tests pass | Case 1: Final Commit |
-> | There are still incomplete steps, unresolved fixes, or waiting actions | Case 2: More Work Needed |
-> | The purpose of this commit is to send the implementation/refinement into code review | Case 3: Ready for Review |
-> | Code is committed, review is done, and the next action should be PR creation | Case 4: Ready for PR |
->
-> **Do not mix multiple cases. You must decide first, then output the single matching next step.**
-
-### Case 1: Final Commit (Trigger: all work is done and the next step is task archival)
-
-If this is the last commit and all work is done:
-
-Prerequisites:
-- [ ] All code committed
-- [ ] All tests pass
-- [ ] Code review passed
-- [ ] All workflow steps complete
-
-Suggest next step:
-
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
-
-```
-Next step - complete and archive the task:
-  - Claude Code / OpenCode: /complete-task {task-id}
-  - Gemini CLI: /{{project}}:complete-task {task-id}
-  - Codex CLI: $complete-task {task-id}
-```
-
-### Case 2: More Work Needed (Trigger: incomplete steps, unresolved issues, or pending collaboration remain)
+> The full four-case status matrix, prerequisite checks, and multi-TUI next-step commands live in `reference/task-status-update.md`. Read `reference/task-status-update.md` before updating task state.
 
-If there's follow-up work (awaiting review, more fixes needed):
-- Update `task.md`: set `updated_at` to current time
-- Record this commit's content and next steps in task.md
+Append the Commit Activity Log entry and choose exactly one next-step case:
+- final commit -> `complete-task {task-id}`
+- more work remains -> update task.md and stop
+- ready for review -> `review-task {task-id}`
+- ready for PR -> `create-pr`
 
-### Case 3: Ready for Review (Trigger: the next action should be `review-task`)
-
-If the commit is ready for code review:
-- Update `task.md`: set `current_step` to `code-review`
-- Update `task.md`: set `updated_at` to current time
-- Mark implementation step as complete in workflow progress
-
-Suggest next step:
-
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
-
-```
-Next step - code review:
-  - Claude Code / OpenCode: /review-task {task-id}
-  - Gemini CLI: /{{project}}:review-task {task-id}
-  - Codex CLI: $review-task {task-id}
-```
-
-### Case 4: Ready for PR (Trigger: the next action should be `create-pr`)
-
-If the commit should become a Pull Request:
-- Update `task.md`: set `updated_at` to current time
-- Record PR plan in task.md
-
-Suggest next step:
+## Notes
 
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+- Never commit secrets such as `.env`, credentials, or keys
+- Keep the current agent first in the co-author block
+- Do not use `git add -A` or `git add .`
 
-```
-Next step - create a Pull Request:
-  - Claude Code / OpenCode: /create-pr
-  - Gemini CLI: /{{project}}:create-pr
-  - Codex CLI: $create-pr
-```
-
-## Notes
+## Error Handling
 
-- Do NOT commit files containing sensitive information (.env, credentials, etc.)
-- Ensure commit messages clearly describe the changes
-- Follow the project's Conventional Commits conventions
-- If task status update fails, warn the user but do not block the commit
+- If the task status update fails, warn the user but do not block the commit

package/templates/.agents/skills/commit/SKILL.zh-CN.md

@@ -1,138 +1,40 @@
 ---
 name: commit
-description: >
-  提交当前变更到 Git，包含版权头年份检查和任务状态更新。
-  当用户要求提交代码或保存变更时触发。
+description: "提交当前变更到 Git"
 ---
 
 # 提交代码
 
-提交当前变更到 Git。
+在不覆盖用户本地工作的前提下创建 Git commit，并在需要时更新关联任务状态。
 
-## 步骤 0：检查本地修改（关键）
+## 1. 检查本地修改（关键）
 
-**强制步骤**：在任何编辑之前，你**必须**检查用户的本地修改以避免覆盖其工作。
+在任何编辑前先检查：
 
 ```bash
 git status --short
 git diff
 ```
 
-**规则**：
-1. **仔细阅读 `git diff` 输出** —— 理解用户已经做了哪些修改
-2. **在用户修改基础上进行增量编辑** —— 不要覆盖其实现
-3. **如果你计划的编辑与用户修改冲突**，先询问用户：
-   ```
-   This file has local modifications:
-   - Your changes: [描述用户的修改]
-   - My planned changes: [描述计划的修改]
-   Please confirm how to proceed.
-   ```
-4. **不要**重写用户已实现的代码
-5. **不要**添加用户没有要求的"改进"
+必须尊重现有用户改动；如果你的计划与之冲突，先停止并征求确认。
 
-## 步骤 1：更新版权头年份（关键）
+## 2. 更新版权头年份
 
-**强制步骤**：提交之前，检查并更新所有修改文件的版权头。
+动态获取当前年份，只更新已经改动过的文件。
 
-### 获取当前年份
+> 完整版权检查流程见 `reference/copyright-check.md`。修改任何版权头前，先读取 `reference/copyright-check.md`。
 
-```bash
-date +%Y
-```
-
-**绝不硬编码年份。**
-
-### 检查修改的文件
-
-```bash
-git status --short
-```
-
-### 对每个修改的文件
-
-检查文件是否有版权头：
-```bash
-grep "Copyright.*[0-9]\{4\}" <modified_file>
-```
-
-如果有版权头且年份不是当前年份，更新年份。
-
-**常见格式**：
-- `Copyright (C) 2024-2025` -> `Copyright (C) 2024-{CURRENT_YEAR}`
-- `Copyright (C) 2024` -> `Copyright (C) 2024-{CURRENT_YEAR}`
-- `Copyright (C) 2025` -> `Copyright (C) {CURRENT_YEAR}`（如果已是当前年份）
-
-### 版权检查清单
-
-执行 `git commit` 之前：
-- [ ] 使用 `date +%Y` 动态获取当前年份
-- [ ] 检查了所有即将提交的文件
-- [ ] 更新了所有有版权头的文件的版权年份
-- [ ] **绝不**硬编码年份
-- [ ] **仅**更新修改的文件，而非整个项目
-
-## 步骤 2：分析变更并生成提交信息
-
-```bash
-git status
-git diff
-git log --oneline -5
-```
-
-生成 Conventional Commits 格式的提交信息：
-- `<type>(<scope>): <subject>`（英文祈使语气，不超过 50 字符）
-- Body：2-4 个要点说明修改了什么以及为什么
-- 署名块：
-  - `Co-Authored-By: {你的模型名称} <noreply@provider.com>`
-  - 如果与任务相关，追加其他贡献 Agent 的 `Co-Authored-By` 行
-
-### 多 Agent 协作署名（仅任务相关提交）
-
-如果本次提交属于某个活动任务，且存在 `.agent-workspace/active/{task-id}/task.md`：
-
-1. 读取 `task.md` 中的 `## Activity Log` 部分。
-2. 从符合 `by {agent}` 的条目中提取所有唯一 Agent 名称；可使用较宽松的匹配模式，例如 `by (\S+)`。
-3. 排除 `human`，因为 Git author 已经是人类用户。
-4. 将 Agent 名称映射为 `Co-Authored-By` 行：
-
-| Agent | 署名 |
-|-------|------|
-| `claude` | `Co-Authored-By: Claude <noreply@anthropic.com>` |
-| `codex` | `Co-Authored-By: Codex <noreply@openai.com>` |
-| `gemini` | `Co-Authored-By: Gemini <noreply@google.com>` |
-| `opencode` | `Co-Authored-By: OpenCode <noreply@opencode.ai>` |
-
-5. 构建署名块时遵循以下规则：
-   - 保持当前执行提交的 Agent 署名在原有位置。
-   - 将其他唯一参与 Agent 作为额外的 `Co-Authored-By` 行追加。
-   - 如果当前 Agent 已在 `Activity Log` 中出现，不要重复追加。
-   - 未知 Agent 名称使用兜底格式 `Co-Authored-By: {Agent} <noreply@unknown>`。
-
-如果本次提交与任务无关，保持原有单行署名行为不变。
-
-## 步骤 3：创建提交
+## 3. 生成提交信息
 
-```bash
-git add <specific-files>
-git commit -m "$(cat <<'EOF'
-<type>(<scope>): <subject>
+检查状态、diff 和最近历史，然后按 Conventional Commits 生成 message，并补齐正确的协作署名。
 
-- <要点 1>
-- <要点 2>
+> 提交信息规则、示例和多代理署名细节见 `reference/commit-message.md`。写 commit message 前先读取 `reference/commit-message.md`。
 
-Co-Authored-By: {你的模型名称} <noreply@provider.com>
-<其他任务参与者的额外 Co-Authored-By 行（如有）>
-EOF
-)"
-```
+## 4. 创建提交
 
-**重要**：
-- 按名称添加特定文件 —— 不要使用 `git add -A` 或 `git add .`
-- 不要提交可能包含密钥的文件（.env、凭据、密钥）
-- 对于任务相关提交，保持当前 Agent 署名在前，并在其后追加上面生成的额外署名行
+只暂存明确列出的文件，然后执行 `git commit`。
 
-## 步骤 4：更新任务状态（如果与任务相关）
+## 5. 按需更新任务状态
 
 获取当前时间：
 
@@ -140,93 +42,20 @@ EOF
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-提交后，根据情况更新任务状态：
-
-对于以下所有情况，**追加**到 task.md 的 `## Activity Log`（不要覆盖之前的记录）：
-```
-- {yyyy-MM-dd HH:mm:ss} — **Commit** by {agent} — {commit hash short} {commit subject}
-```
-
-> **⚠️ 情况判断 — 你必须先核对任务状态，再从下面 4 种情况中精确匹配唯一分支：**
->
-> - 检查 `task.md` 的 `current_step`、工作流进度和 `## Activity Log` 最新记录
-> - 检查是否存在最新 `review.md` / `review-r{N}.md`，以及最新审查是否为“通过且无问题”
-> - 检查是否仍有待处理的修复、审查或 PR 创建步骤
->
-> | 判断依据 | 必须选择的情况 |
-> |---------|---------------|
-> | 所有工作流步骤完成 + 最新审查通过且无问题 + 所有测试通过 | 情况 1：最终提交 |
-> | 仍有未完成步骤、待修复问题或等待他人动作 | 情况 2：还有后续工作 |
-> | 当前提交的目的就是把实现/修复结果送入代码审查 | 情况 3：准备审查 |
-> | 代码已提交且审查已完成，下一步应创建 PR | 情况 4：准备创建 PR |
->
-> **禁止同时套用多个情况。必须先判断，再输出唯一匹配的下一步。**
-
-### 情况 1：最终提交（触发条件：所有工作已完成，下一步是归档任务）
-
-如果这是最后一次提交且所有工作已完成：
-
-前置条件：
-- [ ] 所有代码已提交
-- [ ] 所有测试通过
-- [ ] 代码审查通过
-- [ ] 所有工作流步骤完成
-
-建议下一步：
-
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
-
-```
-下一步 - 完成并归档任务：
-  - Claude Code / OpenCode：/complete-task {task-id}
-  - Gemini CLI：/{{project}}:complete-task {task-id}
-  - Codex CLI：$complete-task {task-id}
-```
-
-### 情况 2：还有后续工作（触发条件：仍有未完成步骤、待修复项或待协作事项）
+> 完整的 4 种状态分支、前置条件检查和多 TUI 下一步命令见 `reference/task-status-update.md`。更新任务状态前，先读取 `reference/task-status-update.md`。
 
-如果有后续工作（等待审查、需要更多修复）：
-- 更新 `task.md`：设置 `updated_at` 为当前时间
-- 在 task.md 中记录此次提交的内容和下一步
+追加 Commit 的 Activity Log，并且只能选择一个下一步分支：
+- 最终提交 -> `complete-task {task-id}`
+- 还有后续工作 -> 更新 task.md 后停止
+- 准备审查 -> `review-task {task-id}`
+- 准备创建 PR -> `create-pr`
 
-### 情况 3：准备审查（触发条件：下一步应执行 `review-task`）
-
-如果提交已准备好进行代码审查：
-- 更新 `task.md`：设置 `current_step` 为 `code-review`
-- 更新 `task.md`：设置 `updated_at` 为当前时间
-- 在工作流进度中标记 implementation 步骤为已完成
-
-建议下一步：
-
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
-
-```
-下一步 - 代码审查：
-  - Claude Code / OpenCode：/review-task {task-id}
-  - Gemini CLI：/{{project}}:review-task {task-id}
-  - Codex CLI：$review-task {task-id}
-```
-
-### 情况 4：准备创建 PR（触发条件：下一步应执行 `create-pr`）
-
-如果提交应该创建 Pull Request：
-- 更新 `task.md`：设置 `updated_at` 为当前时间
-- 在 task.md 中记录 PR 计划
-
-建议下一步：
+## 注意事项
 
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+- 不要提交 `.env`、凭据、密钥等敏感文件
+- 协作署名中当前代理必须排在最前面
+- 不要使用 `git add -A` 或 `git add .`
 
-```
-下一步 - 创建 Pull Request：
-  - Claude Code / OpenCode：/create-pr
-  - Gemini CLI：/{{project}}:create-pr
-  - Codex CLI：$create-pr
-```
-
-## 注意事项
+## 错误处理
 
-- 不要提交包含敏感信息的文件（.env、凭据等）
-- 确保提交信息清晰描述变更内容
-- 遵循项目的 Conventional Commits 规范
-- 如果任务状态更新失败，警告用户但不要阻止提交
+- 如果任务状态更新失败，警告用户，但不要因此阻止提交

package/templates/.agents/skills/commit/reference/commit-message.md

@@ -0,0 +1,60 @@
+# Commit Message Rules
+
+Read this file before staging files or composing the commit message.
+
+## Analyze Changes and Generate the Commit Message
+
+```bash
+git status
+git diff
+git log --oneline -5
+```
+
+Generate a Conventional Commit:
+- `<type>(<scope>): <subject>`
+- imperative English subject, under 50 characters
+- 2-4 body bullets describing what changed and why
+
+### Multi-Agent Co-Authorship
+
+If the commit belongs to an active task:
+1. read `## Activity Log` in task.md
+2. collect unique agent names from `by {agent}`
+3. exclude `human`
+4. map agents to `Co-Authored-By` lines
+
+| Agent | Co-Authored-By line |
+|---|---|
+| `claude` | `Co-Authored-By: Claude <noreply@anthropic.com>` |
+| `codex` | `Co-Authored-By: Codex <noreply@openai.com>` |
+| `gemini` | `Co-Authored-By: Gemini <noreply@google.com>` |
+| `opencode` | `Co-Authored-By: OpenCode <noreply@opencode.ai>` |
+
+Build the co-author block with these rules:
+1. keep the current executing agent first
+2. append other unique participating agents after it
+3. if the current agent already appears in Activity Log, do not add a duplicate line
+4. de-duplicate all additional `Co-Authored-By` lines
+5. map unknown agents to `Co-Authored-By: {Agent} <noreply@unknown>`
+
+## Create the Commit
+
+```bash
+git add <specific-files>
+git commit -m "$(cat <<'EOF'
+<type>(<scope>): <subject>
+
+- <bullet point 1>
+- <bullet point 2>
+
+Co-Authored-By: {Your Model Name} <noreply@provider.com>
+<additional Co-Authored-By lines>
+EOF
+)"
+```
+
+Important:
+- add specific files only
+- do not use `git add -A` or `git add .`
+- do not include secrets
+- keep the current agent first in the co-author block

package/templates/.agents/skills/commit/reference/commit-message.zh-CN.md

@@ -0,0 +1,60 @@
+# 提交信息规则
+
+在暂存文件或编写 commit message 之前先读取本文件。
+
+## 分析变更并生成提交信息
+
+```bash
+git status
+git diff
+git log --oneline -5
+```
+
+生成 Conventional Commit：
+- `<type>(<scope>): <subject>`
+- `subject` 必须使用英文祈使句，且不超过 50 个字符
+- 正文使用 2-4 条 bullet，说明改了什么以及为什么改
+
+### 多 Agent 共同署名
+
+如果该提交属于一个活动中的任务：
+1. 读取 task.md 中的 `## Activity Log`
+2. 从 `by {agent}` 中收集去重后的 agent 名称
+3. 排除 `human`
+4. 将 agent 映射为 `Co-Authored-By` 行
+
+| Agent | Co-Authored-By 行 |
+|---|---|
+| `claude` | `Co-Authored-By: Claude <noreply@anthropic.com>` |
+| `codex` | `Co-Authored-By: Codex <noreply@openai.com>` |
+| `gemini` | `Co-Authored-By: Gemini <noreply@google.com>` |
+| `opencode` | `Co-Authored-By: OpenCode <noreply@opencode.ai>` |
+
+按以下规则构建 co-author 区块：
+1. 当前执行的 agent 必须放在第一行
+2. 其余参与过的唯一 agent 追加在后面
+3. 如果当前 agent 已经出现在 Activity Log 中，不要重复追加同一行
+4. 所有额外的 `Co-Authored-By` 行都要去重
+5. 未知 agent 统一映射为 `Co-Authored-By: {Agent} <noreply@unknown>`
+
+## 创建提交
+
+```bash
+git add <specific-files>
+git commit -m "$(cat <<'EOF'
+<type>(<scope>): <subject>
+
+- <bullet point 1>
+- <bullet point 2>
+
+Co-Authored-By: {Your Model Name} <noreply@provider.com>
+<additional Co-Authored-By lines>
+EOF
+)"
+```
+
+重要约束：
+- 只能添加明确指定的文件
+- 不要使用 `git add -A` 或 `git add .`
+- 不要提交任何敏感信息
+- co-author 区块必须把当前 agent 放在第一行

package/templates/.agents/skills/commit/reference/copyright-check.md

@@ -0,0 +1,39 @@
+# Copyright Check
+
+Read this file before editing any copyright header.
+
+## Update Copyright Header Years
+
+### Get Current Year
+
+```bash
+date +%Y
+```
+
+### Check Modified Files
+
+```bash
+git status --short
+```
+
+### For Each Modified File
+
+Check whether the file contains a copyright header:
+
+```bash
+grep "Copyright.*[0-9]\{4\}" <modified_file>
+```
+
+If a header exists and the year is outdated, update it using the current year.
+
+Common update patterns:
+- `Copyright (C) 2024-2025` -> `Copyright (C) 2024-{CURRENT_YEAR}`
+- `Copyright (C) 2024` -> `Copyright (C) 2024-{CURRENT_YEAR}`
+- `Copyright (C) 2025` -> `Copyright (C) {CURRENT_YEAR}` when the file already uses the current year
+
+### Copyright Checklist
+
+- [ ] Use `date +%Y`
+- [ ] Check every modified file
+- [ ] Update only modified files
+- [ ] Never hardcode the current year