@fitlab-ai/agent-infra 0.5.7 → 0.5.9

package/templates/.agents/skills/create-issue/reference/label-and-type.en.md

@@ -1,71 +0,0 @@
-# Labels, Issue Type, and Milestone Rules
-
-Read this file before applying labels, Issue Type, milestone, or `in:` labels.
-
-## Default Body Format (Fallback)
-
-Recommended fallback:
-
-```markdown
-## Description
-
-{task-description}
-
-## Requirements
-
-- [ ] {requirement-1}
-- [ ] {requirement-2}
-```
-
-Map task types to GitHub labels and Issue Types, but keep only labels that actually exist.
-
-Fallback label mapping:
-
-| task.md type | GitHub label |
-|---|---|
-| `bug`, `bugfix` | `type: bug` |
-| `feature` | `type: feature` |
-| `enhancement` | `type: enhancement` |
-| `docs`, `documentation` | `type: documentation` |
-| `dependency-upgrade` | `type: dependency-upgrade` |
-| `task`, `chore` | `type: task` |
-| `refactor`, `refactoring` | `type: enhancement` |
-| other values | skip |
-
-Issue Type fallback mapping:
-
-| task.md type | GitHub Issue Type |
-|---|---|
-| `bug`, `bugfix` | `Bug` |
-| `feature`, `enhancement` | `Feature` |
-| `task`, `documentation`, `dependency-upgrade`, `chore`, `docs`, `refactor`, `refactoring`, and all other values | `Task` |
-
-## Create the Issue
-
-Before creating the Issue, read `.agents/rules/issue-pr-commands.md` and use its "Create an Issue" command template.
-
-Before calling the creation command, follow `.agents/rules/issue-sync.md` / `.agents/rules/issue-pr-commands.md` to complete the prerequisite authentication and code-hosting platform detection steps.
-
-If no valid labels remain, omit label arguments.
-
-For milestone inference, read `.agents/rules/milestone-inference.md` and follow "Phase 1: `create-issue`" before creating the Issue.
-
-Issue Type setup follows the matching commands in `.agents/rules/issue-pr-commands.md`.
-
-- handle direct writes for labels, milestones, `in:` labels, and Issue Type by following the permission-degradation rules in `.agents/rules/issue-pr-commands.md` and `.agents/rules/issue-sync.md`
-- when those rules say to skip a direct write, continue without failing Issue creation
-
-`in:` labels (coarse selection):
-
-Prepare label edit arguments by following the Issue update command in `.agents/rules/issue-pr-commands.md`.
-
-Use the returned labels to do semantic matching against the task.md title and description:
-- add a label when the task **explicitly mentions** a module (for example, "fix CLI argument parsing" -> `in: cli`)
-- add a label when the task **strongly implies** a module
-- skip the label when the mapping is ambiguous or uncertain
-
-Principle: prefer missing labels over wrong labels. Coarse selection does not need to be perfect because implement-task / create-pr will refine `in:` labels from actual changed files later.
-
-Handle relevant `in:` labels by following the permission-degradation rules in `.agents/rules/issue-sync.md`. Do not fail Issue creation when `in:` labels are unavailable, irrelevant, or skipped by those rules.
-
-Skip unavailable labels, Issue Types, or milestones without failing the Issue creation flow.

package/templates/.agents/skills/create-issue/reference/label-and-type.zh-CN.md

@@ -1,71 +0,0 @@
-# Label、Issue Type 和 Milestone 规则
-
-在应用 label、Issue Type、milestone 或 `in:` label 之前先读取本文件。
-
-## 默认正文格式（Fallback）
-
-推荐 fallback：
-
-```markdown
-## Description
-
-{task-description}
-
-## Requirements
-
-- [ ] {requirement-1}
-- [ ] {requirement-2}
-```
-
-将任务类型映射到 GitHub label 和 Issue Type，但只保留仓库里实际存在的 label。
-
-Fallback label 映射：
-
-| task.md type | GitHub label |
-|---|---|
-| `bug`, `bugfix` | `type: bug` |
-| `feature` | `type: feature` |
-| `enhancement` | `type: enhancement` |
-| `docs`, `documentation` | `type: documentation` |
-| `dependency-upgrade` | `type: dependency-upgrade` |
-| `task`, `chore` | `type: task` |
-| `refactor`, `refactoring` | `type: enhancement` |
-| 其他值 | 跳过 |
-
-Issue Type fallback 映射：
-
-| task.md type | GitHub Issue Type |
-|---|---|
-| `bug`, `bugfix` | `Bug` |
-| `feature`, `enhancement` | `Feature` |
-| `task`, `documentation`, `dependency-upgrade`, `chore`, `docs`, `refactor`, `refactoring` 以及其他所有值 | `Task` |
-
-## 创建 Issue
-
-创建 Issue 时，执行前先读取 `.agents/rules/issue-pr-commands.md`，并使用其中的 “创建 Issue” 命令模板。
-
-调用创建命令前，先按 `.agents/rules/issue-sync.md` / `.agents/rules/issue-pr-commands.md` 完成前置步骤中的认证和代码托管平台检测。
-
-如果最终没有有效 label，就省略 label 参数。
-
-Milestone 推断规则见 `.agents/rules/milestone-inference.md` 的「阶段 1：`create-issue`」。推断前先读取该文件。
-
-Issue Type 设置同样遵循 `.agents/rules/issue-pr-commands.md` 中的对应命令。
-
-- Label、milestone、`in:` label 和 Issue Type 的直接设置，都按 `.agents/rules/issue-pr-commands.md` 与 `.agents/rules/issue-sync.md` 的权限降级规则处理
-- 当规则判定应跳过直接写入时，继续创建 Issue，不要让流程失败
-
-`in:` label（粗选）：
-
-执行前先按 `.agents/rules/issue-pr-commands.md` 的 Issue 更新命令准备 label 编辑参数。
-
-从查询结果中，根据 task.md 的标题和描述进行语义匹配：
-- 任务描述**明确提及**某个模块（如"修复 CLI 参数解析"→ `in: cli`）→ 添加
-- 任务描述**强烈暗示**某个模块 → 添加
-- 无法确定或模糊 → **不添加**
-
-原则：宁缺毋滥。粗选阶段不求精确，后续 implement-task / create-pr 阶段会基于实际改动文件精修。
-
-相关 `in:` label 的添加按 `.agents/rules/issue-sync.md` 的权限降级规则处理。当 `in:` label 不可用、不相关或规则判定应跳过时，不要让创建 Issue 流程失败。
-
-当 label、Issue Type 或 milestone 不可用时，应跳过并继续，不要让 Issue 创建失败。

package/templates/.agents/skills/create-issue/reference/template-matching.en.md

@@ -1,45 +0,0 @@
-# Issue Template Matching
-
-Read this file before deciding how to build the Issue body from `.github/ISSUE_TEMPLATE`.
-
-## Detect Issue Templates
-
-Search project templates with:
-
-```bash
-rg --files .github/ISSUE_TEMPLATE -g '*.yml' -g '!config.yml'
-```
-
-If templates exist, inspect their top-level `name:` fields and choose the best match for the task title and description.
-
-Typical candidate templates:
-- `bug_report.yml` for bug work
-- `question.yml` for question or investigation work
-- `feature_request.yml` for feature work
-- `documentation.yml` for documentation work
-- `other.yml` as the general fallback
-
-If no template matches clearly, choose the nearest candidate. If templates are missing, unreadable, or parsing fails, fall back to the default body path.
-
-## Build the Body from the Matched Template
-
-Read the matched template's:
-- `name`
-- `type:`
-- `labels:`
-- `body:`
-
-Field handling rules:
-- `textarea` and `input`: use `attributes.label` as the markdown heading and fill values from task.md
-- `markdown`: skip template explanation prose
-- `dropdown` and `checkboxes`: skip
-- when task.md lacks a suitable value, write `N/A`
-
-Suggested field mapping:
-
-| Template field hint | task.md source |
-|---|---|
-| `summary`, `title` | task title |
-| `description`, `problem`, `what happened`, `issue-description`, `current-content` | task description |
-| `solution`, `requirements`, `steps`, `suggested-content`, `impact`, `context`, `alternatives`, `expected` | requirements list |
-| other `textarea` / `input` fields | task description, otherwise `N/A` |

package/templates/.agents/skills/create-issue/reference/template-matching.zh-CN.md

@@ -1,45 +0,0 @@
-# Issue 模板匹配
-
-在决定如何从 `.github/ISSUE_TEMPLATE` 构建 Issue 正文之前先读取本文件。
-
-## 探测 Issue 模板
-
-用下面的命令搜索项目模板：
-
-```bash
-rg --files .github/ISSUE_TEMPLATE -g '*.yml' -g '!config.yml'
-```
-
-如果模板存在，检查其顶层 `name:` 字段，并为当前任务标题和描述选择最匹配的模板。
-
-常见候选模板：
-- `bug_report.yml`：用于 bug 类工作
-- `question.yml`：用于问题排查或调研类工作
-- `feature_request.yml`：用于功能类工作
-- `documentation.yml`：用于文档类工作
-- `other.yml`：通用 fallback
-
-如果没有明显匹配的模板，选择最接近的候选项。如果模板缺失、不可读取或解析失败，就回退到默认正文路径。
-
-## 使用匹配到的模板构建正文
-
-读取匹配模板中的：
-- `name`
-- `type:`
-- `labels:`
-- `body:`
-
-字段处理规则：
-- `textarea` 和 `input`：使用 `attributes.label` 作为 Markdown 标题，并从 task.md 填充值
-- `markdown`：跳过模板解释性文字
-- `dropdown` 和 `checkboxes`：跳过
-- 当 task.md 没有合适值时，写入 `N/A`
-
-建议字段映射：
-
-| 模板字段提示 | task.md 来源 |
-|---|---|
-| `summary`, `title` | 任务标题 |
-| `description`, `problem`, `what happened`, `issue-description`, `current-content` | 任务描述 |
-| `solution`, `requirements`, `steps`, `suggested-content`, `impact`, `context`, `alternatives`, `expected` | 需求列表 |
-| 其他 `textarea` / `input` 字段 | 优先使用任务描述，否则写 `N/A` |

package/templates/.claude/commands/create-issue.en.md

@@ -1,8 +0,0 @@
----
-description: "Create a GitHub Issue from a task file"
-usage: "/create-issue <task-id>"
----
-
-Read and execute the create-issue skill from `.agents/skills/create-issue/SKILL.md`.
-
-Follow all steps defined in the skill exactly.

package/templates/.claude/commands/create-issue.zh-CN.md

@@ -1,8 +0,0 @@
----
-description: "从任务文件创建 GitHub Issue"
-usage: "/create-issue <task-id>"
----
-
-读取并执行 `.agents/skills/create-issue/SKILL.md` 中的 create-issue 技能。
-
-严格按照技能中定义的所有步骤执行。

package/templates/.gemini/commands/_project_/create-issue.en.toml

@@ -1,8 +0,0 @@
-description = "Create a GitHub Issue from a task file"
-prompt = """
-Create Issue for task {{args}}.
-
-Read and execute the create-issue skill from `.agents/skills/create-issue/SKILL.md`.
-
-Follow all steps defined in the skill exactly.
-"""

package/templates/.gemini/commands/_project_/create-issue.zh-CN.toml

@@ -1,8 +0,0 @@
-description = "从任务文件创建 GitHub Issue"
-prompt = """
-为任务 {{args}} 创建 Issue。
-
-读取并执行 `.agents/skills/create-issue/SKILL.md` 中的 create-issue 技能。
-
-严格按照技能中定义的所有步骤执行。
-"""

package/templates/.opencode/commands/create-issue.en.md

@@ -1,11 +0,0 @@
----
-description: "Create a GitHub Issue from a task file"
-agent: general
-subtask: false
----
-
-Create Issue for task $1.
-
-Read and execute the create-issue skill from `.agents/skills/create-issue/SKILL.md`.
-
-Follow all steps defined in the skill exactly.

package/templates/.opencode/commands/create-issue.zh-CN.md

@@ -1,11 +0,0 @@
----
-description: "从任务文件创建 GitHub Issue"
-agent: general
-subtask: false
----
-
-为任务 $1 创建 Issue。
-
-读取并执行 `.agents/skills/create-issue/SKILL.md` 中的 create-issue 技能。
-
-严格按照技能中定义的所有步骤执行。