gitadmin
ff41e7965a
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.
Forge Skills
A collection of specialized forge interaction skills for GitHub and Gitea.
Overview
This directory contains focused skills for interacting with different code hosting platforms:
- GitHub: Use
/forge-githubfor GitHub repositories, issues, pull requests, releases, or CI - Gitea: Use
/forge-giteafor Gitea repositories, issues, pull requests, releases, or CI - Router: Use
/forge-interactionto let the system choose the right skill automatically
Skill Structure
Each forge-specific skill is designed with:
- Single Responsibility: Handles only one forge type (GitHub or Gitea)
- Predictable Behavior: Clear decision tree and completion criteria
- Complete Coverage: All requested forge actions are supported
- Error Handling: Specific guidance for missing tools or authentication
Choosing the Right Skill
Use /forge-github when:
- Working with GitHub repositories (
github.comURLs) - Using the
ghCLI tool - Interacting with GitHub-specific features (issues, PRs, releases, CI)
Use /forge-gitea when:
- Working with Gitea repositories (
gitea.comor self-hosted Gitea) - Using the
teaCLI tool - Interacting with Gitea-specific features (issues, PRs, releases, CI)
Use /forge-interaction when:
- You're unsure which forge you're working with
- You want the system to automatically choose the right skill
- You prefer a unified interface that handles both platforms
Skill Comparison
| Feature | GitHub Skill | Gitea Skill |
|---|---|---|
| CLI Tool | gh |
tea |
| Platform | GitHub | Gitea |
| Focus | GitHub-specific | Gitea-specific |
| Predictability | High | High |
| Maintenance | Isolated | Isolated |
Usage Examples
# For GitHub work
/forge-github create an issue in this repo
/forge-github list pull requests
/forge-github check CI status
/forge-github publish a new release
# For Gitea work
/forge-gitea create an issue in this repo
/forge-gitea list pull requests
/forge-gitea check CI status
/forge-gitea publish a new release
# Let the system decide
/forge-interaction create a PR for this feature
Why Separate Skills?
- Predictability: Each skill knows exactly one forge type
- Maintainability: Changes to GitHub or Gitea logic stay isolated
- Clarity: Users can see which forge a skill handles at a glance
- Testing: Each skill can be tested independently
- Cognitive Load: Users remember fewer skills and their specific purposes
Related Skills
/forge-router- High-level guidance for choosing the right forge skill/forge-preferences- Personal or project-specific forge configurations
Next Steps
- Choose the appropriate skill based on your forge platform
- Ensure the required CLI tool (
ghortea) is installed - Configure authentication for your forge platform
- Start with simple actions and build up to more complex workflows