rename skills

2026-04-17 14:25:30 +08:00
parent 192f7545d5
commit 1175e69cd2
9 changed files with 20 additions and 20 deletions
@@ -1,5 +1,5 @@
 ---
-name: coding-standards
+name: rui-coding-standards
 description: Enforces coding quality rules including static typing, test coverage thresholds, test framework requirements, TDD practices, and tooling constraints. Load this skill before implementing any code changes.
 ---

@@ -1,5 +1,5 @@
 ---
-name: commit-standards
+name: rui-commit-standards
 description: Rules for commit messages, branch hygiene, and commit integrity. Covers Conventional Changelog format, atomic single-issue commits, rebase-only policy, and required commit message structure.
 ---

@@ -55,5 +55,5 @@ and build integrity.
 ## Build Integrity

 - Every commit must leave the full build passing. Run all quality gates before
-  committing (see `coding-standards` skill for the full list).
+  committing (see `rui-coding-standards` skill for the full list).
 - Never commit code that breaks any stage of the build pipeline.
@@ -1,5 +1,5 @@
 ---
-name: parallel-agents
+name: rui-parallel-agents
 description: Multi-agent coordination strategy for parallel development across branches. Covers clone setup, git identity, branch isolation, push strategy, verification, and final reporting.
 ---

@@ -25,9 +25,9 @@ Each parallel agent must:
   ```
   git remote add upstream /app
   ```
-4. **Configure git identity** using the credentials from the `project-identity` skill.
+4. **Configure git identity** using the credentials from the `rui-project-identity` skill.
 5. **Work on their assigned branch** following the full task execution workflow
-   (see `task-workflow` skill).
+   (see `rui-task-workflow` skill).
 6. **Push to both origin and upstream** when done:
   ```
   git push -u origin <branch-name>
@@ -1,5 +1,5 @@
 ---
-name: pr-fix-process
+name: rui-pr-fix-process
 description: Workflow for fixing a PR based on review comments. Covers reading reviews, amend-and-force-push strategy, implementation notes, PR description updates, review responses, and new ticket policy.
 ---

@@ -19,7 +19,7 @@ description: Workflow for fixing a PR based on review comments. Covers reading r
 ## Fix Strategy

 All fixes are applied by **amending the existing commit** and **force pushing** the branch.
-This maintains a clean, atomic commit history consistent with the `commit-standards` skill:
+This maintains a clean, atomic commit history consistent with the `rui-commit-standards` skill:

 ```bash
 # Make code changes
@@ -83,7 +83,7 @@ If a review comment points to work that is outside the scope of the current tick

 After all fixes are applied:

-1. **Run all quality gates** per the `coding-standards` skill (lint, typecheck, unit tests,
+1. **Run all quality gates** per the `rui-coding-standards` skill (lint, typecheck, unit tests,
   integration tests, coverage >= 97%).
 2. **Amend the commit** with any quality gate fixes.
 3. **Force push** the branch.
@@ -1,5 +1,5 @@
 ---
-name: pr-review-process
+name: rui-pr-review-process
 description: PR code review methodology including focus areas, multi-agent review strategy, reporting format, verdict criteria, and Forgejo posting behavior.
 ---

@@ -1,5 +1,5 @@
 ---
-name: project-identity
+name: rui-project-identity
 description: Project-specific configuration including role identity, Forgejo server details, git credentials, authentication setup, and reference materials for the current project.
 ---

@@ -1,5 +1,5 @@
 ---
-name: search-issues
+name: rui-search-issues
 description: Search Forgejo issues and pull requests by keyword with local matching, filtering, and pagination. Use this when you need to find specific tickets in a large repository.
 ---

@@ -10,7 +10,7 @@ fetched page by page from the API and matched client-side against title and
 body text. This avoids the unreliable server-side search and gives precise
 substring matching with AND/OR logic.

-**Prerequisites:** Load the `project-identity` skill first to get the Forgejo
+**Prerequisites:** Load the `rui-project-identity` skill first to get the Forgejo
 server URL, API token, and repository name needed for the required options.

 ## Script location
@@ -1,5 +1,5 @@
 ---
-name: task-discovery
+name: rui-task-discovery
 description: Rules for finding, filtering, and prioritizing work from the Forgejo issue tracker. Covers assignee filtering, state label requirements, priority ordering, and blocked issue handling.
 ---

@@ -1,5 +1,5 @@
 ---
-name: task-workflow
+name: rui-task-workflow
 description: End-to-end task execution lifecycle for Forgejo issues. Covers preparation, implementation with TDD, quality gates, commit/push, pull request creation, issue state transitions, and discovering new work.
 ---

@@ -14,15 +14,15 @@ description: End-to-end task execution lifecycle for Forgejo issues. Covers prep
   blocker is resolved first, remove the `Blocked` label, then transition to
   `State/In Progress`.
 4. **Set up the branch.** Use the branch name from the issue's Metadata > Branch field.
-   See the `commit-standards` skill for branch setup commands.
+   See the `rui-commit-standards` skill for branch setup commands.

 ## Phase 2: Implementation

 5. **Work through the subtasks in order.** Complete each subtask listed in the issue body.
   As you complete each one, update the issue body via the Forgejo API to check it off
   (`- [x]`).
-6. **Write tests alongside code.** Follow TDD as described in the `coding-standards` skill.
-7. **Handle obsolete tests.** See the `coding-standards` skill for the policy on updating
+6. **Write tests alongside code.** Follow TDD as described in the `rui-coding-standards` skill.
+7. **Handle obsolete tests.** See the `rui-coding-standards` skill for the policy on updating
   vs. fixing tests during redesign.
 8. **Add implementation notes as Forgejo issue comments.** Throughout your work, generously
   and exhaustively append detailed comments to the Forgejo issue documenting:
@@ -43,12 +43,12 @@ description: End-to-end task execution lifecycle for Forgejo issues. Covers prep
 9. **Verify coverage >= 97%.** Run `nox -s coverage_report`. If coverage is below 97%,
   write new tests targeting files with the most uncovered lines. Rerun until met.
 10. **Run the full nox suite.** Run `nox` (all default sessions). Fix any errors, even those
-    that seem unrelated to your commit. See the `coding-standards` skill for the full list
+    that seem unrelated to your commit. See the `rui-coding-standards` skill for the full list
    of required passing stages.

 ## Phase 4: Commit and Push

-11. **Stage and commit.** Follow the `commit-standards` skill for message format.
+11. **Stage and commit.** Follow the `rui-commit-standards` skill for message format.
 12. **Push the branch:**
    ```
    git push -u origin <branch-name>