speckit-taskstoissues skill hardcoded for GitHub, non-functional on Gitea-hosted repos #2

New Issue

2026-08-02T21:13:24+03:00

issuer-agent commented

2026-08-02 21:13:24 +03:00

Why: The vendored speckit-taskstoissues skill (.claude/skills/speckit-taskstoissues/SKILL.md) contains a hard caution gate:

> [!CAUTION]
> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

This gate blocks the skill from proceeding on any Gitea-hosted repo. Additionally, the skill's documented workflow references the "GitHub MCP server's list_issues tool" and "GitHub MCP server to create a new issue" — but this fleet uses mcp__plugin_cluster_gitea-tools__* for all Gitea work, and the GitHub MCP is not wired for this purpose.

Result: /speckit-taskstoissues cannot be invoked on any repo using Gitea (i.e., the entire oleks/* fleet), even though other spec-kit skills (e.g. speckit-implement) already use the correct mcp__plugin_cluster_gitea-tools__* conventions.

Repro: Invoked speckit-taskstoissues on oracle-adb-backend (remote: git@git.oleks.space:oleks/oracle-adb-backend.git) on 2026-08-02. The skill's caution gate refused to proceed because the remote is not a GitHub URL.

Acceptance:

Remove or conditionally gate the GitHub-URL check in speckit-taskstoissues (or accept Gitea URLs)
Replace hardcoded GitHub MCP tool calls (list_issues, issue creation) with conditional dispatch to either GitHub MCP or mcp__plugin_cluster_gitea-tools__* based on repo remote
Test the skill on a Gitea-hosted repo to confirm it backfills issues from tasks.md

Related: Related to (but separate from) oleks/claude-plugin-spec-kit#1, which covered upstream CLI flag drift. This issue is specific to the GitHub-vs-Gitea MCP tooling assumption in this skill.

**Why**: The vendored `speckit-taskstoissues` skill (`.claude/skills/speckit-taskstoissues/SKILL.md`) contains a hard caution gate: ``` > [!CAUTION] > ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL ``` This gate blocks the skill from proceeding on any Gitea-hosted repo. Additionally, the skill's documented workflow references the "GitHub MCP server's `list_issues` tool" and "GitHub MCP server to create a new issue" — but this fleet uses `mcp__plugin_cluster_gitea-tools__*` for all Gitea work, and the GitHub MCP is not wired for this purpose. Result: `/speckit-taskstoissues` cannot be invoked on any repo using Gitea (i.e., the entire oleks/* fleet), even though other spec-kit skills (e.g. `speckit-implement`) already use the correct `mcp__plugin_cluster_gitea-tools__*` conventions. **Repro**: Invoked `speckit-taskstoissues` on `oracle-adb-backend` (remote: `git@git.oleks.space:oleks/oracle-adb-backend.git`) on 2026-08-02. The skill's caution gate refused to proceed because the remote is not a GitHub URL. **Acceptance**: - [ ] Remove or conditionally gate the GitHub-URL check in `speckit-taskstoissues` (or accept Gitea URLs) - [ ] Replace hardcoded GitHub MCP tool calls (`list_issues`, issue creation) with conditional dispatch to either GitHub MCP or `mcp__plugin_cluster_gitea-tools__*` based on repo remote - [ ] Test the skill on a Gitea-hosted repo to confirm it backfills issues from `tasks.md` **Related**: Related to (but separate from) oleks/claude-plugin-spec-kit#1, which covered upstream CLI flag drift. This issue is specific to the GitHub-vs-Gitea MCP tooling assumption in this skill.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: oleks/claude-plugin-spec-kit#2