diff --git a/skills/coding-standards/SKILL.md b/skills/rui-coding-standards/SKILL.md similarity index 99% rename from skills/coding-standards/SKILL.md rename to skills/rui-coding-standards/SKILL.md index a00768e..b39eff3 100644 --- a/skills/coding-standards/SKILL.md +++ b/skills/rui-coding-standards/SKILL.md @@ -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. --- diff --git a/skills/commit-standards/SKILL.md b/skills/rui-commit-standards/SKILL.md similarity index 95% rename from skills/commit-standards/SKILL.md rename to skills/rui-commit-standards/SKILL.md index 625a173..727198f 100644 --- a/skills/commit-standards/SKILL.md +++ b/skills/rui-commit-standards/SKILL.md @@ -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. diff --git a/skills/parallel-agents/SKILL.md b/skills/rui-parallel-agents/SKILL.md similarity index 93% rename from skills/parallel-agents/SKILL.md rename to skills/rui-parallel-agents/SKILL.md index 364ceb1..f0ac607 100644 --- a/skills/parallel-agents/SKILL.md +++ b/skills/rui-parallel-agents/SKILL.md @@ -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 diff --git a/skills/pr-fix-process/SKILL.md b/skills/rui-pr-fix-process/SKILL.md similarity index 96% rename from skills/pr-fix-process/SKILL.md rename to skills/rui-pr-fix-process/SKILL.md index 0ae6f0a..18ec85c 100644 --- a/skills/pr-fix-process/SKILL.md +++ b/skills/rui-pr-fix-process/SKILL.md @@ -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. diff --git a/skills/pr-review-process/SKILL.md b/skills/rui-pr-review-process/SKILL.md similarity index 99% rename from skills/pr-review-process/SKILL.md rename to skills/rui-pr-review-process/SKILL.md index 5b51373..7fc50d7 100644 --- a/skills/pr-review-process/SKILL.md +++ b/skills/rui-pr-review-process/SKILL.md @@ -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. --- diff --git a/skills/project-identity/SKILL.md b/skills/rui-project-identity/SKILL.md similarity index 98% rename from skills/project-identity/SKILL.md rename to skills/rui-project-identity/SKILL.md index f5d7e0f..b9cec25 100644 --- a/skills/project-identity/SKILL.md +++ b/skills/rui-project-identity/SKILL.md @@ -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. --- diff --git a/skills/search-issues/SKILL.md b/skills/rui-search-issues/SKILL.md similarity index 98% rename from skills/search-issues/SKILL.md rename to skills/rui-search-issues/SKILL.md index 70478a3..f4d6f44 100644 --- a/skills/search-issues/SKILL.md +++ b/skills/rui-search-issues/SKILL.md @@ -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 diff --git a/skills/task-discovery/SKILL.md b/skills/rui-task-discovery/SKILL.md similarity index 98% rename from skills/task-discovery/SKILL.md rename to skills/rui-task-discovery/SKILL.md index cd45252..36e396a 100644 --- a/skills/task-discovery/SKILL.md +++ b/skills/rui-task-discovery/SKILL.md @@ -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. --- diff --git a/skills/task-workflow/SKILL.md b/skills/rui-task-workflow/SKILL.md similarity index 91% rename from skills/task-workflow/SKILL.md rename to skills/rui-task-workflow/SKILL.md index 6d74e70..c156322 100644 --- a/skills/task-workflow/SKILL.md +++ b/skills/rui-task-workflow/SKILL.md @@ -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