@fitlab-ai/agent-infra 0.3.0

package/templates/.agents/skills/create-pr/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: create-pr
+description: >
+  Create a Pull Request to the specified or auto-detected target branch.
+  Triggered when the user requests PR creation.
+  Optional argument: target branch.
+---
+
+# Create Pull Request
+
+Create a Pull Request. Optional argument: target branch.
+
+## Execution Flow
+
+### 1. Determine Target Branch
+
+- If user provided an argument (e.g. `main`, `develop`, `3.6.x`), use it as target branch
+- If no argument, auto-detect:
+  ```bash
+  git branch --show-current
+  git log --oneline --decorate --first-parent -20
+  ```
+  **Detection rules**:
+  - Currently on a main/trunk branch -> target is that branch
+  - Currently on a feature branch -> find the nearest parent branch from log decorations
+  - Cannot determine -> ask the user
+
+### 2. Read PR Template
+
+Read `.github/PULL_REQUEST_TEMPLATE.md` from the repository.
+
+If the template doesn't exist, use a standard format.
+
+### 3. Review Recent Merged PRs for Reference
+
+```bash
+gh pr list --limit 3 --state merged --json number,title,body
+```
+
+Use these as style and format reference.
+
+### 4. Analyze Current Branch Changes
+
+```bash
+git status
+git log <target-branch>..HEAD --oneline
+git diff <target-branch>...HEAD --stat
+git diff <target-branch>...HEAD
+```
+
+Understand all commits and changes that will be in this PR. Look at ALL commits, not just the latest one.
+
+### 5. Check Remote Branch Status
+
+```bash
+git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
+```
+
+### 6. Push If Not Yet Pushed
+
+```bash
+git push -u origin <current-branch>
+```
+
+### 7. Create PR
+
+- Follow `.github/PULL_REQUEST_TEMPLATE.md` format for all sections
+- Reference recent merged PRs for style
+- Use HEREDOC format to pass the body
+- PR must end with: `Generated with AI assistance`
+
+```bash
+gh pr create --base <target-branch> --title "<title>" --body "$(cat <<'EOF'
+<Complete PR description following template>
+
+Generated with AI assistance
+EOF
+)"
+```
+
+### 8. Update Task Status (If Task-Related)
+
+Get the current time:
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+If there is an active task for this work, update `.agent-workspace/active/{task-id}/task.md`:
+- `pr_number`: {pr-number}
+- `updated_at`: {current time}
+- **Append** to `## Activity Log` (do NOT overwrite previous entries):
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **PR Created** by {agent} — PR #{pr-number} created
+  ```
+
+### 9. Output Result
+
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
+```
+PR created: {pr-url}
+
+Next steps (if in task workflow):
+- Sync progress:
+  - Claude Code / OpenCode: /sync-pr {task-id}
+  - Gemini CLI: /{{project}}:sync-pr {task-id}
+  - Codex CLI: $sync-pr {task-id}
+- Complete task:
+  - Claude Code / OpenCode: /complete-task {task-id}
+  - Gemini CLI: /{{project}}:complete-task {task-id}
+  - Codex CLI: $complete-task {task-id}
+```
+
+## Notes
+
+1. **Follow PR template**: Fill in all required sections from the template
+2. **Reference style**: Match the format and style of recent merged PRs
+3. **Title format**: Follow Conventional Commits or project conventions
+4. **All commits matter**: Analyze ALL commits in the branch, not just the latest
+
+## Error Handling
+
+- No commits to push: Prompt "No commits found between {target} and HEAD"
+- Push rejected: Suggest `git pull --rebase` first
+- PR already exists: Show existing PR URL

package/templates/.agents/skills/create-pr/SKILL.zh-CN.md

@@ -0,0 +1,125 @@
+---
+name: create-pr
+description: >
+  创建 Pull Request 到指定或自动推断的目标分支。
+  当用户要求创建 PR 时触发。可选参数：目标分支。
+---
+
+# 创建 Pull Request
+
+创建 Pull Request。可选参数：目标分支。
+
+## 执行流程
+
+### 1. 确定目标分支
+
+- 如果用户提供了参数（例如 `main`、`develop`、`3.6.x`），使用其作为目标分支
+- 如果没有参数，自动检测：
+  ```bash
+  git branch --show-current
+  git log --oneline --decorate --first-parent -20
+  ```
+  **检测规则**：
+  - 当前在 main/trunk 分支 -> 目标是该分支
+  - 当前在 feature 分支 -> 从日志装饰中找到最近的父分支
+  - 无法确定 -> 询问用户
+
+### 2. 读取 PR 模板
+
+从仓库中读取 `.github/PULL_REQUEST_TEMPLATE.md`。
+
+如果模板不存在，使用标准格式。
+
+### 3. 参考最近合并的 PR
+
+```bash
+gh pr list --limit 3 --state merged --json number,title,body
+```
+
+以此作为风格和格式参考。
+
+### 4. 分析当前分支变更
+
+```bash
+git status
+git log <target-branch>..HEAD --oneline
+git diff <target-branch>...HEAD --stat
+git diff <target-branch>...HEAD
+```
+
+理解将包含在此 PR 中的所有提交和变更。查看**所有**提交，而不仅仅是最新的。
+
+### 5. 检查远程分支状态
+
+```bash
+git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
+```
+
+### 6. 如未推送则先推送
+
+```bash
+git push -u origin <current-branch>
+```
+
+### 7. 创建 PR
+
+- 遵循 `.github/PULL_REQUEST_TEMPLATE.md` 格式填写所有部分
+- 参考最近合并的 PR 的风格
+- 使用 HEREDOC 格式传递 body
+- PR 必须以 `Generated with AI assistance` 结尾
+
+```bash
+gh pr create --base <target-branch> --title "<title>" --body "$(cat <<'EOF'
+<按模板填写的完整 PR 描述>
+
+Generated with AI assistance
+EOF
+)"
+```
+
+### 8. 更新任务状态（如果与任务相关）
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+如果有关联的活跃任务，更新 `.agent-workspace/active/{task-id}/task.md`：
+- `pr_number`：{pr-number}
+- `updated_at`：{当前时间}
+- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **PR Created** by {agent} — PR #{pr-number} created
+  ```
+
+### 9. 输出结果
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+PR 已创建：{pr-url}
+
+下一步（如在任务工作流中）：
+- 同步进度：
+  - Claude Code / OpenCode：/sync-pr {task-id}
+  - Gemini CLI：/{{project}}:sync-pr {task-id}
+  - Codex CLI：$sync-pr {task-id}
+- 完成任务：
+  - Claude Code / OpenCode：/complete-task {task-id}
+  - Gemini CLI：/{{project}}:complete-task {task-id}
+  - Codex CLI：$complete-task {task-id}
+```
+
+## 注意事项
+
+1. **遵循 PR 模板**：填写模板中所有必要部分
+2. **参考风格**：匹配最近合并的 PR 的格式和风格
+3. **标题格式**：遵循 Conventional Commits 或项目规范
+4. **所有提交都重要**：分析分支中的**所有**提交，而不仅仅是最新的
+
+## 错误处理
+
+- 无提交可推送：提示 "No commits found between {target} and HEAD"
+- 推送被拒绝：建议先执行 `git pull --rebase`
+- PR 已存在：显示已有的 PR URL

package/templates/.agents/skills/create-release-note/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: create-release-note
+description: >
+  Generate release notes from PRs and commits between two versions.
+  Triggered when the user requests release note generation.
+  Arguments: version number, optional previous version.
+---
+
+# Create Release Notes
+
+Generate comprehensive release notes for a version based on merged PRs and commits.
+
+## Execution Flow
+
+### Step 1: Parse Arguments
+
+From arguments:
+- `<version>`: Current release version (required), format `X.Y.Z`
+- `<prev-version>`: Previous version (optional), auto-detected if not provided
+
+### Step 2: Determine Version Range
+
+**Current tag**: `v<version>`
+
+**Previous tag** (if not specified):
+```bash
+git tag --sort=-v:refname
+```
+Find the most recent tag before `v<version>`.
+
+**Verify tags exist**:
+```bash
+git rev-parse v<version>
+git rev-parse v<prev-version>
+```
+
+### Step 3: Reference Historical Release Notes Format
+
+Fetch the most recent published release notes as a format reference:
+
+```bash
+# Get the latest non-draft release tag
+gh release list --limit 5 --json tagName,isDraft,isPrerelease \
+  --jq '[.[] | select(.isDraft == false and .isPrerelease == false)][0].tagName'
+
+# Get the release body
+gh release view <latest-tag> --json body -q '.body'
+```
+
+**Purpose**:
+- Analyze the section structure, heading style, emoji usage, and item format of historical release notes
+- When generating release notes in Step 7, **must** follow the historical format to maintain consistency across versions
+- If no historical release notes exist, use the default format defined in Step 7
+
+### Step 4: Collect Merged PRs
+
+Get the date range between tags, then query merged PRs:
+
+```bash
+# Get tag dates
+git log v<prev-version> --format=%aI -1
+git log v<version> --format=%aI -1
+
+# Get merged PRs in range
+gh pr list --state merged --base <branch> \
+  --json number,title,body,author,labels,mergedAt,url \
+  --limit 200 --search "merged:YYYY-MM-DD..YYYY-MM-DD"
+```
+
+Also collect direct commits without PRs:
+```bash
+git log v<prev-version>..v<version> --format="%H %s" --no-merges
+```
+
+### Step 5: Collect Related Issues
+
+From each PR body, extract linked Issues:
+- Match patterns: `Closes #N`, `Fixes #N`, `Resolves #N` (case-insensitive)
+
+```bash
+gh issue view <N> --json number,title,labels,url
+```
+
+### Step 6: Classify Changes
+
+**By type** (from PR title conventional commit prefix):
+- `feat`, `perf`, `refactor`, dependency upgrades -> Enhancement
+- `fix` -> Bugfix
+- `docs` -> Documentation (merge into Enhancement if fewer than 3 items)
+
+**By module** (from PR title scope, labels, or file paths):
+- Infer module from PR title brackets like `[module]` or conventional scope `feat(module):`
+- Fallback: analyze changed files
+
+### Step 7: Generate Release Notes
+
+**Prioritize the historical format obtained in Step 3.** If historical release notes exist, strictly follow their section structure, heading style (including emojis), item format, and bilingual layout.
+
+If no historical release notes exist, use the following default Markdown format:
+
+```markdown
+## {Module/Platform Name}
+
+### Enhancement
+
+- [{scope}] Description by @author in [#N](url)
+
+### Bugfix
+
+- [{scope}] Description by @author in [#N](url)
+
+## Contributors
+
+@contributor1, @contributor2, @contributor3
+```
+
+**Format rules**:
+1. Item format: `- [scope] Description by @author in [#N](url)`
+2. Issue + PR: `in [#Issue](url) and [#PR](url)`
+3. Description: Use PR title, remove `type(scope):` prefix, capitalize first letter
+4. Contributors: Deduplicated, sorted by contribution count (descending)
+5. Empty sections: Omit sections with no entries
+
+### Step 8: Present and Confirm
+
+Show the generated release notes to the user.
+
+Ask:
+1. Need any adjustments?
+2. Create a GitHub Draft Release?
+
+### Step 9: Create Draft Release (If Confirmed)
+
+```bash
+gh release create v<version> \
+  --title "v<version>" \
+  --notes-file /tmp/release-notes-v<version>.md \
+  --draft
+```
+
+Output:
+```
+Draft Release created.
+
+- URL: {draft-release-url}
+- Version: v{version}
+- Status: Draft
+
+Please review and publish on GitHub:
+1. Open the URL above
+2. Review the release notes
+3. Click "Publish release"
+```
+
+## Notes
+
+1. **Requires gh CLI**: Must have GitHub CLI installed and authenticated
+2. **Tags must exist**: Run the release skill first to create tags
+3. **Draft mode**: Creates a draft - won't auto-publish
+4. **Classification accuracy**: Auto-classification is based on title/scope/files; complex PRs may need manual adjustment
+
+## Error Handling
+
+- Invalid version format: Prompt correct format
+- Tag not found: Suggest running the release skill first
+- gh not authenticated: Prompt to authenticate
+- No merged PRs found: Prompt to check tags and branch

package/templates/.agents/skills/create-release-note/SKILL.zh-CN.md

@@ -0,0 +1,166 @@
+---
+name: create-release-note
+description: >
+  从 PR 和 commit 生成版本发布说明。
+  当用户要求生成发布说明时触发。参数：版本号，可选的上一版本号。
+---
+
+# 创建发布说明
+
+基于已合并的 PR 和提交，为指定版本生成全面的发布说明。
+
+## 执行流程
+
+### 步骤 1：解析参数
+
+从参数中提取：
+- `<version>`：当前发布版本（必需），格式 `X.Y.Z`
+- `<prev-version>`：上一版本（可选），如未提供则自动检测
+
+### 步骤 2：确定版本范围
+
+**当前标签**：`v<version>`
+
+**上一标签**（如未指定）：
+```bash
+git tag --sort=-v:refname
+```
+查找 `v<version>` 之前最近的标签。
+
+**验证标签存在**：
+```bash
+git rev-parse v<version>
+git rev-parse v<prev-version>
+```
+
+### 步骤 3：参考历史发布说明格式
+
+获取最近一次已发布的 Release Note 作为格式参考：
+
+```bash
+# 获取最近的非草稿 Release 标签
+gh release list --limit 5 --json tagName,isDraft,isPrerelease \
+  --jq '[.[] | select(.isDraft == false and .isPrerelease == false)][0].tagName'
+
+# 获取该 Release 的 body
+gh release view <latest-tag> --json body -q '.body'
+```
+
+**用途**：
+- 分析历史发布说明的章节结构、标题风格、emoji 使用、条目格式
+- 后续步骤 7 生成发布说明时，**必须**优先遵循历史格式，保持版本间的一致性
+- 如果没有历史发布说明，则使用步骤 7 中定义的默认格式
+
+### 步骤 4：收集已合并的 PR
+
+获取标签之间的日期范围，然后查询已合并的 PR：
+
+```bash
+# 获取标签日期
+git log v<prev-version> --format=%aI -1
+git log v<version> --format=%aI -1
+
+# 获取范围内已合并的 PR
+gh pr list --state merged --base <branch> \
+  --json number,title,body,author,labels,mergedAt,url \
+  --limit 200 --search "merged:YYYY-MM-DD..YYYY-MM-DD"
+```
+
+同时收集没有 PR 的直接提交：
+```bash
+git log v<prev-version>..v<version> --format="%H %s" --no-merges
+```
+
+### 步骤 5：收集关联 Issue
+
+从每个 PR body 中提取关联的 Issue：
+- 匹配模式：`Closes #N`、`Fixes #N`、`Resolves #N`（不区分大小写）
+
+```bash
+gh issue view <N> --json number,title,labels,url
+```
+
+### 步骤 6：分类变更
+
+**按类型**（从 PR 标题的 Conventional Commit 前缀）：
+- `feat`、`perf`、`refactor`、依赖升级 -> Enhancement
+- `fix` -> Bugfix
+- `docs` -> Documentation（如少于 3 项则合并到 Enhancement）
+
+**按模块**（从 PR 标题 scope、标签或文件路径）：
+- 从 PR 标题中的方括号 `[module]` 或 Conventional scope `feat(module):` 推断模块
+- 兜底：分析变更的文件
+
+### 步骤 7：生成发布说明
+
+**优先使用步骤 3 中获取的历史格式**。如果存在历史发布说明，严格沿用其章节结构、标题风格（含 emoji）、条目格式和双语布局。
+
+如果没有历史发布说明，使用以下默认格式化为 Markdown：
+
+```markdown
+## {模块/平台名称}
+
+### Enhancement
+
+- [{scope}] Description by @author in [#N](url)
+
+### Bugfix
+
+- [{scope}] Description by @author in [#N](url)
+
+## Contributors
+
+@contributor1, @contributor2, @contributor3
+```
+
+**格式规则**：
+1. 条目格式：`- [scope] Description by @author in [#N](url)`
+2. Issue + PR：`in [#Issue](url) and [#PR](url)`
+3. 描述：使用 PR 标题，移除 `type(scope):` 前缀，首字母大写
+4. 贡献者：去重，按贡献数量降序排列
+5. 空部分：省略没有条目的部分
+
+### 步骤 8：展示并确认
+
+向用户展示生成的发布说明。
+
+询问：
+1. 需要调整吗？
+2. 是否创建 GitHub Draft Release？
+
+### 步骤 9：创建 Draft Release（如确认）
+
+```bash
+gh release create v<version> \
+  --title "v<version>" \
+  --notes-file /tmp/release-notes-v<version>.md \
+  --draft
+```
+
+输出：
+```
+Draft Release created.
+
+- URL: {draft-release-url}
+- Version: v{version}
+- Status: Draft
+
+Please review and publish on GitHub:
+1. Open the URL above
+2. Review the release notes
+3. Click "Publish release"
+```
+
+## 注意事项
+
+1. **需要 gh CLI**：必须安装并认证 GitHub CLI
+2. **标签必须存在**：先执行 release 技能创建标签
+3. **草稿模式**：创建草稿 —— 不会自动发布
+4. **分类准确性**：自动分类基于标题/scope/文件；复杂的 PR 可能需要手动调整
+
+## 错误处理
+
+- 版本格式无效：提示正确格式
+- 标签未找到：建议先执行 release 技能
+- gh 未认证：提示进行认证
+- 未找到已合并的 PR：提示检查标签和分支