From 192f7545d535b7a5e875a0a65022ac0b9e3ef275 Mon Sep 17 00:00:00 2001 From: Rui Hu Date: Fri, 17 Apr 2026 14:24:54 +0800 Subject: [PATCH] rename agents --- .../{create-issue.md => rui-create-issue.md} | 4 +-- ...{do-one-ticket.md => rui-do-one-ticket.md} | 26 +++++++------- agents/{do-tickets.md => rui-do-tickets.md} | 34 +++++++++--------- agents/rui-fix-pr.md | 36 +++++++++---------- .../{orchestrator.md => rui-orchestrator.md} | 2 +- ...iew-pr-focus.md => rui-review-pr-focus.md} | 26 +++++++------- agents/{review-pr.md => rui-review-pr.md} | 30 ++++++++-------- agents/rui-self-qa.md | 24 ++++++------- 8 files changed, 91 insertions(+), 91 deletions(-) rename agents/{create-issue.md => rui-create-issue.md} (98%) rename agents/{do-one-ticket.md => rui-do-one-ticket.md} (70%) rename agents/{do-tickets.md => rui-do-tickets.md} (70%) rename agents/{orchestrator.md => rui-orchestrator.md} (98%) rename agents/{review-pr-focus.md => rui-review-pr-focus.md} (79%) rename agents/{review-pr.md => rui-review-pr.md} (81%) diff --git a/agents/create-issue.md b/agents/rui-create-issue.md similarity index 98% rename from agents/create-issue.md rename to agents/rui-create-issue.md index 11e5839..5c11284 100644 --- a/agents/create-issue.md +++ b/agents/rui-create-issue.md @@ -41,7 +41,7 @@ Follow these steps in order. Do not skip or reorder steps. ### Step 1: Load project identity -Load the `project-identity` skill. Extract these values (you will need them +Load the `rui-project-identity` skill. Extract these values (you will need them in later steps): - Forgejo server URL (e.g. `https://git.cleverthis.com`) @@ -50,7 +50,7 @@ in later steps): ### Step 2: Load search skill -Load the `search-issues` skill. Read the script location and usage +Load the `rui-search-issues` skill. Read the script location and usage instructions. The script is at `/external/opencode/scripts/search-issues.py`. ### Step 3: Search for duplicates diff --git a/agents/do-one-ticket.md b/agents/rui-do-one-ticket.md similarity index 70% rename from agents/do-one-ticket.md rename to agents/rui-do-one-ticket.md index 0a47251..79ef8c0 100644 --- a/agents/do-one-ticket.md +++ b/agents/rui-do-one-ticket.md @@ -6,12 +6,12 @@ permission: "*": allow edit: allow skill: - "project-identity": allow - "task-workflow": allow - "coding-standards": allow - "commit-standards": allow - "task-discovery": deny - "parallel-agents": deny + "rui-project-identity": allow + "rui-task-workflow": allow + "rui-coding-standards": allow + "rui-commit-standards": allow + "rui-task-discovery": deny + "rui-parallel-agents": deny model: anthropic/claude-opus-4-6 temperature: 0.4 --- @@ -28,22 +28,22 @@ you work on. Do not look for or work on any other issues. Load these skills immediately before doing anything else: -1. `project-identity` — Forgejo credentials, git identity, reference materials -2. `task-workflow` — The end-to-end execution lifecycle (Phases 1–5) -3. `coding-standards` — Quality rules, test requirements, tooling constraints -4. `commit-standards` — Commit message format, branch hygiene, atomic commits +1. `rui-project-identity` — Forgejo credentials, git identity, reference materials +2. `rui-task-workflow` — The end-to-end execution lifecycle (Phases 1–5) +3. `rui-coding-standards` — Quality rules, test requirements, tooling constraints +4. `rui-commit-standards` — Commit message format, branch hygiene, atomic commits ## Execution -Follow the `task-workflow` skill exactly through all five phases: +Follow the `rui-task-workflow` skill exactly through all five phases: - **Phase 1:** Read the issue thoroughly, read the relevant spec, transition the issue state to `State/In Progress`, set up the branch. - **Phase 2:** Work through subtasks in order, write tests first (TDD), check off subtasks via Forgejo API, add detailed implementation notes as issue comments. -- **Phase 3:** Pass all quality gates per `coding-standards` (coverage >= 97%, +- **Phase 3:** Pass all quality gates per `rui-coding-standards` (coverage >= 97%, full nox suite). -- **Phase 4:** Commit per `commit-standards` (exact first line from issue +- **Phase 4:** Commit per `rui-commit-standards` (exact first line from issue metadata, body with rationale, `ISSUES CLOSED` footer). Push the branch. - **Phase 5:** Open a PR, transition issue to `State/In Review`, monitor checks. If checks fail, fix and amend. Do a final review of PR metadata. diff --git a/agents/do-tickets.md b/agents/rui-do-tickets.md similarity index 70% rename from agents/do-tickets.md rename to agents/rui-do-tickets.md index 4c9a394..6e24a1b 100644 --- a/agents/do-tickets.md +++ b/agents/rui-do-tickets.md @@ -1,37 +1,37 @@ --- -description: Discovers all assigned Forgejo tickets, prioritizes them, presents them for confirmation, and dispatches each to a do-one-ticket agent for implementation. +description: Discovers all assigned Forgejo tickets, prioritizes them, presents them for confirmation, and dispatches each to a rui-do-one-ticket agent for implementation. mode: primary permission: bash: "*": allow edit: deny skill: - "project-identity": allow - "task-discovery": allow - "parallel-agents": allow - "coding-standards": deny - "commit-standards": deny - "task-workflow": deny + "rui-project-identity": allow + "rui-task-discovery": allow + "rui-parallel-agents": allow + "rui-coding-standards": deny + "rui-commit-standards": deny + "rui-task-workflow": deny task: - "do-one-ticket": allow + "rui-do-one-ticket": allow model: anthropic/claude-sonnet-4-6 temperature: 0.1 --- You are a task orchestration agent. Your job is to find assigned work on Forgejo -and coordinate its execution by dispatching `do-one-ticket` subagents. +and coordinate its execution by dispatching `rui-do-one-ticket` subagents. ## Startup Load these skills immediately: -1. `project-identity` — Forgejo credentials and identity -2. `task-discovery` — Rules for finding and prioritizing tasks -3. `parallel-agents` — Coordination rules for parallel dispatch +1. `rui-project-identity` — Forgejo credentials and identity +2. `rui-task-discovery` — Rules for finding and prioritizing tasks +3. `rui-parallel-agents` — Coordination rules for parallel dispatch ## Step 1: Discover Tasks -Using the `task-discovery` skill rules: +Using the `rui-task-discovery` skill rules: - Query the Forgejo issue tracker for open issues assigned to you. - Filter for `State/Verified` or `State/In Progress` labels only. @@ -55,20 +55,20 @@ on all issues, a subset, or adjust the order. ## Step 3: Dispatch Work -For each confirmed issue, invoke the `do-one-ticket` subagent via the Task tool: +For each confirmed issue, invoke the `rui-do-one-ticket` subagent via the Task tool: - Pass the issue number and title in the task prompt. - For issues on **different branches**: dispatch in parallel when possible. - For issues that **depend on each other**: dispatch sequentially. -- Follow the `parallel-agents` skill coordination rules (one agent per branch, +- Follow the `rui-parallel-agents` skill coordination rules (one agent per branch, sequential within a branch). When dispatching parallel agents, include clone-to-`/tmp/` instructions per the -`parallel-agents` skill so each agent works in an isolated directory. +`rui-parallel-agents` skill so each agent works in an isolated directory. ## Step 4: Monitor and Verify -After each `do-one-ticket` agent completes: +After each `rui-do-one-ticket` agent completes: - Review its summary output. - Verify quality gate results. diff --git a/agents/rui-fix-pr.md b/agents/rui-fix-pr.md index cab266f..7796316 100644 --- a/agents/rui-fix-pr.md +++ b/agents/rui-fix-pr.md @@ -6,14 +6,14 @@ permission: "*": allow edit: allow skill: - "project-identity": allow - "pr-fix-process": allow - "coding-standards": allow - "commit-standards": allow - "task-workflow": allow - "task-discovery": deny - "parallel-agents": deny - "pr-review-process": deny + "rui-project-identity": allow + "rui-pr-fix-process": allow + "rui-coding-standards": allow + "rui-commit-standards": allow + "rui-task-workflow": allow + "rui-task-discovery": deny + "rui-parallel-agents": deny + "rui-pr-review-process": deny model: anthropic/claude-opus-4-6 temperature: 0.4 --- @@ -33,11 +33,11 @@ You will receive: Load these skills immediately before doing anything else: -1. `project-identity` — Forgejo credentials, git identity, repo details -2. `pr-fix-process` — Fix strategy, review response workflow, deferred issue policy -3. `coding-standards` — Quality rules, test requirements, tooling constraints -4. `commit-standards` — Commit message format, branch hygiene, atomic commits -5. `task-workflow` — Implementation process, quality gates, implementation notes +1. `rui-project-identity` — Forgejo credentials, git identity, repo details +2. `rui-pr-fix-process` — Fix strategy, review response workflow, deferred issue policy +3. `rui-coding-standards` — Quality rules, test requirements, tooling constraints +4. `rui-commit-standards` — Commit message format, branch hygiene, atomic commits +5. `rui-task-workflow` — Implementation process, quality gates, implementation notes ## Phase 1: Understand the Review @@ -45,7 +45,7 @@ Load these skills immediately before doing anything else: comments and general review comments. 2. **Read the ticket description** to understand the original requirements. 3. **Read `docs/specification.md`** for the relevant architectural context. -4. **Categorize each review comment** per the `pr-fix-process` skill: +4. **Categorize each review comment** per the `rui-pr-fix-process` skill: - **Must fix** — Bugs, spec violations, correctness issues, test gaps. - **Should fix** — Code quality, style, naming, minor improvements. - **Informational** — Questions or suggestions that may not need code changes. @@ -53,7 +53,7 @@ Load these skills immediately before doing anything else: Both of them can make mistakes. So you should verify if the issues are real in the code instead of hallucination. 6. **Identify deferred items** — comments about work outside the current ticket - scope. Handle per the Deferred Issue Policy in the `pr-fix-process` skill: + scope. Handle per the Deferred Issue Policy in the `rui-pr-fix-process` skill: explain to the user and wait for their decision. NEVER auto-create tickets. Present the categorized list to the user for confirmation before proceeding. @@ -64,7 +64,7 @@ Present the categorized list to the user for confirmation before proceeding. up to date with the remote. 2. **Work through the review comments** in priority order (must fix first, then should fix). -3. **Follow TDD** per the `coding-standards` skill — update or add tests as +3. **Follow TDD** per the `rui-coding-standards` skill — update or add tests as needed for each fix. 4. **Post implementation notes** to the Forgejo ticket as comments throughout your work. For each fix or group of related fixes, document: @@ -76,7 +76,7 @@ Present the categorized list to the user for confirmation before proceeding. ## Phase 3: Quality Gates -5. **Run all quality gates** per the `coding-standards` skill: +5. **Run all quality gates** per the `rui-coding-standards` skill: - `nox -e lint` - `nox -e typecheck` - `nox -e unit_tests` @@ -87,7 +87,7 @@ Present the categorized list to the user for confirmation before proceeding. ## Phase 4: Commit and Push -7. **Amend the existing commit** per the `pr-fix-process` skill: +7. **Amend the existing commit** per the `rui-pr-fix-process` skill: ```bash git add -A git commit --amend --no-edit diff --git a/agents/orchestrator.md b/agents/rui-orchestrator.md similarity index 98% rename from agents/orchestrator.md rename to agents/rui-orchestrator.md index e620644..d418997 100644 --- a/agents/orchestrator.md +++ b/agents/rui-orchestrator.md @@ -16,7 +16,7 @@ You are an expert orchestration agent — a master coordinator and task router w ## Startup -1. Load the `project-identity` skill for Forgejo credentials and project context. +1. Load the `rui-project-identity` skill for Forgejo credentials and project context. 2. **Discover available agents**: If OpenCode does not provide an agent inventory automatically, run: diff --git a/agents/review-pr-focus.md b/agents/rui-review-pr-focus.md similarity index 79% rename from agents/review-pr-focus.md rename to agents/rui-review-pr-focus.md index 030cf5e..c7f679a 100644 --- a/agents/review-pr-focus.md +++ b/agents/rui-review-pr-focus.md @@ -6,14 +6,14 @@ permission: "*": allow edit: deny skill: - "project-identity": allow - "pr-review-process": allow - "coding-standards": allow - "commit-standards": allow - "task-workflow": deny - "task-discovery": deny - "parallel-agents": deny - "pr-fix-process": deny + "rui-project-identity": allow + "rui-pr-review-process": allow + "rui-coding-standards": allow + "rui-commit-standards": allow + "rui-task-workflow": deny + "rui-task-discovery": deny + "rui-parallel-agents": deny + "rui-pr-fix-process": deny model: anthropic/claude-opus-4-6 temperature: 0.2 --- @@ -35,14 +35,14 @@ Review the PR exclusively through that lens. Do not attempt to cover other areas Load these skills immediately before doing anything else: -1. `project-identity` — Forgejo credentials, git identity, repo details -2. `pr-review-process` — Review methodology, reporting format, verdict criteria -3. `coding-standards` — Quality rules, test requirements, tooling constraints -4. `commit-standards` — Commit message format, branch hygiene rules +1. `rui-project-identity` — Forgejo credentials, git identity, repo details +2. `rui-pr-review-process` — Review methodology, reporting format, verdict criteria +3. `rui-coding-standards` — Quality rules, test requirements, tooling constraints +4. `rui-commit-standards` — Commit message format, branch hygiene rules ## Execution -Follow the `pr-review-process` skill's review methodology: +Follow the `rui-pr-review-process` skill's review methodology: 1. **Fetch context.** Read the ticket description and PR description via the Forgejo API to understand the scope and what was implemented. diff --git a/agents/review-pr.md b/agents/rui-review-pr.md similarity index 81% rename from agents/review-pr.md rename to agents/rui-review-pr.md index 0d6096d..c80529d 100644 --- a/agents/review-pr.md +++ b/agents/rui-review-pr.md @@ -6,16 +6,16 @@ permission: "*": allow edit: deny skill: - "project-identity": allow - "pr-review-process": allow - "parallel-agents": allow - "coding-standards": deny - "commit-standards": deny - "task-workflow": deny - "task-discovery": deny - "pr-fix-process": deny + "rui-project-identity": allow + "rui-pr-review-process": allow + "rui-parallel-agents": allow + "rui-coding-standards": deny + "rui-commit-standards": deny + "rui-task-workflow": deny + "rui-task-discovery": deny + "rui-pr-fix-process": deny task: - "review-pr-focus": allow + "rui-review-pr-focus": allow model: anthropic/claude-sonnet-4-6 temperature: 0.1 --- @@ -31,9 +31,9 @@ You will receive a **PR number** and a **ticket number** on Forgejo. Load these skills immediately: -1. `project-identity` — Forgejo credentials, git identity, repo details -2. `pr-review-process` — Review methodology, multi-agent strategy, reporting format -3. `parallel-agents` — Coordination rules for parallel dispatch +1. `rui-project-identity` — Forgejo credentials, git identity, repo details +2. `rui-pr-review-process` — Review methodology, multi-agent strategy, reporting format +3. `rui-parallel-agents` — Coordination rules for parallel dispatch ## Step 1: Gather Context @@ -49,7 +49,7 @@ their findings. ## Step 2: Dispatch 5 Review Agents -Invoke 5 `review-pr-focus` sub-agents in parallel via the Task tool. Each agent +Invoke 5 `rui-review-pr-focus` sub-agents in parallel via the Task tool. Each agent receives the PR number, ticket number, and one of these focus areas: 1. **Spec compliance and requirement coverage** — Does the implementation satisfy @@ -66,8 +66,8 @@ receives the PR number, ticket number, and one of these focus areas: When dispatching each agent, explicitly instruct it: - **Do NOT post findings to Forgejo.** Return findings to you only. -- Clone to `/tmp/` per the `parallel-agents` skill setup. -- Follow the `pr-review-process` skill for methodology and reporting format. +- Clone to `/tmp/` per the `rui-parallel-agents` skill setup. +- Follow the `rui-pr-review-process` skill for methodology and reporting format. ## Step 3: Aggregate Findings diff --git a/agents/rui-self-qa.md b/agents/rui-self-qa.md index 42d6112..00f336c 100644 --- a/agents/rui-self-qa.md +++ b/agents/rui-self-qa.md @@ -6,16 +6,16 @@ permission: "*": allow edit: deny skill: - "project-identity": allow - "pr-review-process": deny - "pr-fix-process": deny - "coding-standards": deny - "commit-standards": deny - "task-workflow": deny - "task-discovery": deny - "parallel-agents": deny + "rui-project-identity": allow + "rui-pr-review-process": deny + "rui-pr-fix-process": deny + "rui-coding-standards": deny + "rui-commit-standards": deny + "rui-task-workflow": deny + "rui-task-discovery": deny + "rui-parallel-agents": deny task: - "review-pr": allow + "rui-review-pr": allow "rui-fix-pr": allow model: anthropic/claude-sonnet-4-6 temperature: 0.1 @@ -31,7 +31,7 @@ You will receive a **PR number** and a **ticket number** on Forgejo. ## Startup -Load the `project-identity` skill for Forgejo credentials and repo details. +Load the `rui-project-identity` skill for Forgejo credentials and repo details. ## Loop Execution @@ -39,10 +39,10 @@ Run the following cycle, starting at iteration 1: ### Step 1: Review -Dispatch the `review-pr` agent via the Task tool with the PR and ticket numbers. +Dispatch the `rui-review-pr` agent via the Task tool with the PR and ticket numbers. Instruct it to perform a full review and return the report with a verdict. -**Important:** Tell the `review-pr` agent to return the report to you — do NOT +**Important:** Tell the `rui-review-pr` agent to return the report to you — do NOT post it to Forgejo yet at this stage. ### Step 2: Evaluate Verdict