refactor(forge): split forge-interaction into specialized GitHub and Gitea skills

Break the monolithic forge-interaction skill into focused, single-responsibility skills for better predictability and maintainability: - Add forge-github skill for GitHub-specific interactions using `gh` CLI - Add forge-gitea skill for Gitea-specific interactions using `tea` CLI - Convert forge-interaction into a router that delegates to specialized skills - Add forge-router skill with model invocation disabled for guidance only - Move all forge-related skills to common/deprecated directory Each specialized skill now contains its own complete decision tree, CLI usage patterns, and authentication checks for its respective forge platform.
2026-06-25 12:06:08 -04:00
parent fbca2ada7e
commit ff41e7965a
7 changed files with 459 additions and 13 deletions
@@ -0,0 +1,44 @@
+---
+name: forge-preferences
+description: Use with forge-interaction to apply Steve's personal or project-specific GitHub/Gitea remote, CLI, issue, PR, and release preferences.
+---
+
+# Forge Preferences
+
+Use this companion skill with `/forge-interaction` when personal or project-specific forge preferences are relevant.
+
+## Purpose
+
+Store personal conventions that should not live in the generic forge interaction skill.
+
+## Current Preferences
+
+- If a remote named `forge` exists, treat it as the canonical forge remote.
+- If no `forge` remote exists, use the user's configured default remote when available.
+- If no default remote is configured, use `origin`.
+- Use the forge type of the selected remote to choose the CLI:
+  - GitHub → `gh`
+  - Gitea → `tea`
+- If the correct CLI is missing, tell the user to install it or add it to `PATH`.
+- Do not use the wrong CLI as a fallback.
+
+## Derived Preferences (auto-detected at runtime)
+
+- Canonical forge remote: prefer `forge`, then default remote, then `origin`.
+- Forge CLI: determined from remote URL (GitHub → `gh`, Gitea → `tea`).
+- Known personal Gitea hosts and GitHub usernames/orgs are collected from the remote URL and git CLI at time of use — no hardcoded list.
+
+## Issue Labels
+
+See `triage-labels.md` in this directory for the canonical-to-actual label mapping.
+
+## PR Conventions
+
+- PR titles follow Conventional Commits: `type(scope): description`.
+  - Common types: `feat`, `fix`, `refactor`, `docs`, `chore`, `test`, `style`.
+- PR body is freeform but should summarise the change and any breaking or noteworthy details.
+
+## Release Conventions
+
+- Tags follow semver: `v{major}.{minor}.{patch}` (e.g. `v1.2.3`).
+- Releases are created from the tag with auto-generated or manually curated notes.
@@ -0,0 +1,15 @@
+# Triage Labels
+
+The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
+
+| Label in mattpocock/skills | Label in our tracker | Meaning                                  |
+| -------------------------- | -------------------- | ---------------------------------------- |
+| `needs-triage`             | `needs-triage`       | Maintainer needs to evaluate this issue  |
+| `needs-info`               | `needs-info`         | Waiting on reporter for more information |
+| `ready-for-agent`          | `ready-for-agent`    | Fully specified, ready for an AFK agent  |
+| `ready-for-human`          | `ready-for-human`    | Requires human implementation            |
+| `wontfix`                  | `wontfix`            | Will not be actioned                     |
+
+When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
+
+Edit the right-hand column to match whatever vocabulary you actually use.