issue-operations

This skill routes issue actions by evaluating the session's github.platform and dispatching operations to the appropriate sub-skills, such as github-mcp or gitbucket-api. It acts as a central router to ensure consistent cross-platform governance and behavior.

Yes, you can manage sub-issues and labels across platforms. The router handles creation, commenting, closing, labeling, and sub-issue linking by mapping these user intents to the targeted platform-specific API or local environment.

The best way to enforce bylines and verification gates for issue workflows is through a central routing skill. It enforces strict dispatch contracts and verification requirements before routing operations to platform sub-skills.

Yes, this issue management router works with GitBucket API and local environments. It maintains cross-platform parity by directing actions to github-mcp, gitbucket-api, or local sub-skills based on the current github.platform setting.

To trigger issue creation and commenting, invoke the skill by calling task() with a focused prompt like 'create issue'. The router uses a trigger-dispatch table to map this intent and route the action to the correct platform.