[qodercli] Slash commands not recognized in Qoder IDE 1.24+ — needs skills-based layout migration

[mengqiang81]

Bug Description

The qodercli integration currently scaffolds commands as flat .qoder/commands/speckit.<name>.md files. Starting with Qoder IDE 1.24.0 (released Aug 12, 2026), the IDE no longer scans .qoder/commands/ for slash commands. It only discovers skills in the .qoder/skills/{skill-name}/SKILL.md format (with a name field in frontmatter). This means all /speckit-* commands silently stopped working after the IDE auto-upgraded to 1.24.x.

Steps to Reproduce

1. specify init my-project --integration qodercli (generates .qoder/commands/speckit.*.md)
2. 2. Open the project in Qoder IDE 1.24+
3. 3. Type / in the chat — speckit commands do not appear in the autocomplete list
4. 4. Manually typing /speckit.specify — not recognized (rawCommandCount: 0 in quest.log)

Expected Behavior

The qodercli integration should scaffold skills in the .qoder/skills/speckit-<name>/SKILL.md format, similar to how the claude integration uses .claude/skills/, codex uses .agents/skills/, etc.

Actual Behavior

Qoder IDE 1.24.x no longer scans .qoder/commands/ for slash commands. It only discovers skills in .qoder/skills/{skill-name}/SKILL.md format with a name field in frontmatter. The quest.log shows rawCommandCount:0 after upgrade, confirming the commands are not recognized.

Specify CLI Version

0.16.4

AI Agent

Alquimia AI

Operating System

macOS 26.5.2 (darwin-arm64)

Python Version

Python 3.11.0

Error Logs

Additional Context

Root Cause

Qoder IDE 1.24.x unified slash commands and skills into a single discovery mechanism. Per the official Skills docs, skills must be located at .qoder/skills/{skill-name}/SKILL.md and include a name field in frontmatter.

Suggested Fix

1. Migrate qodercli to a SkillsIntegration subclass
2. 2. Output to .qoder/skills/speckit-<name>/SKILL.md instead of .qoder/commands/speckit.<name>.md
3. 3. Add name: speckit-<name> to frontmatter
4. 4. Use hyphenated naming (speckit-analyze) instead of dotted (speckit.analyze)
5. 5. Provide a migration path for existing installs
6. 6. Update invoke_separator from . to -

[github-actions]

Bug assessment — qodercli-skills-migration: Valid · severity high

---

Bug Assessment: qodercli slash commands not recognized in Qoder IDE 1.24+

• Slug: qodercli-skills-migration
• Created: 2026-08-19T12:47:00Z
• Source: issue [qodercli] Slash commands not recognized in Qoder IDE 1.24+ — needs skills-based layout migration #4199
• Verdict: valid
• Severity: high

Report (summarized)

Reported by @mengqiang81. The qodercli integration scaffolds commands as flat .qoder/commands/speckit.*.md files. Qoder IDE 1.24.0 (released Aug 12, 2026) dropped scanning .qoder/commands/ for slash commands and now only discovers skills in .qoder/skills/{skill-name}/SKILL.md format with a name field in frontmatter. All /speckit-* commands silently stopped working after the IDE auto-upgraded to 1.24.x. The user confirms rawCommandCount: 0 in quest.log post-upgrade.

Specify CLI version: 0.16.4. OS: macOS 26.5.2 darwin-arm64. Python 3.11.0.

Symptom

After Qoder IDE auto-upgrades to 1.24+, all speckit slash commands disappear from autocomplete and manual invocations are not recognized (rawCommandCount: 0). The integration installs files in the old .qoder/commands/ path which the new IDE no longer scans.

Reproduction

1. specify init my-project --integration qodercli — generates .qoder/commands/speckit.*.md
2. Open the project in Qoder IDE 1.24+
3. Type / in the chat — speckit commands do not appear in autocomplete
4. Manually type /speckit.specify — not recognized

Suspected Code Paths

• src/specify_cli/integrations/qodercli/__init__.py:6-21 — QodercliIntegration extends MarkdownIntegration with registrar_config["dir"] = ".qoder/commands" and extension = ".md". This is the direct source of the wrong output layout.
• src/specify_cli/integrations/base.py — SkillsIntegration class provides the skills-based layout (speckit-<name>/SKILL.md) already used by codex, claude, and similar integrations. This is the correct base class for the fix.

Root Cause Hypothesis

QodercliIntegration subclasses MarkdownIntegration and outputs flat .md files under .qoder/commands/. Qoder IDE 1.24.0 unified its command/skill discovery to exclusively use the .qoder/skills/{skill-name}/SKILL.md layout (per the agentskills.io spec). Because the integration has not been updated to match the new layout, all installed commands are simply invisible to the IDE. Confidence: high — the code path is straightforward, the IDE version change is documented in the report, and the SkillsIntegration base class already implements the correct layout for analogous integrations.

Proposed Remediation

Preferred: Migrate QodercliIntegration from MarkdownIntegration to SkillsIntegration, updating config and registrar_config to target .qoder/skills/ with the speckit-<name>/SKILL.md extension pattern — mirroring how CodexIntegration and ClaudeIntegration are implemented:

config["folder"]          = ".qoder/"
config["commands_subdir"] = "skills"
registrar_config["dir"]   = ".qoder/skills"
registrar_config["extension"] = "/SKILL.md"

The SkillsIntegration base class already handles injecting a name field into frontmatter and producing the directory-per-skill layout, so no custom setup() override should be needed. The dotted naming (speckit.analyze) should also be replaced with hyphenated naming (speckit-analyze) to match the new skill directory convention.

A migration notice (or a specify integration reinstall qodercli hint) should be added so existing projects on the old .qoder/commands/ layout get updated.

Alternatives:

• Keep MarkdownIntegration and add a custom setup() that also writes a .qoder/skills/ tree — doubles the output and adds maintenance overhead; not recommended.

Files likely to change:

• src/specify_cli/integrations/qodercli/__init__.py — change base class and config values
• tests/integrations/test_integration_qodercli.py — update expected paths from .qoder/commands/ to .qoder/skills/speckit-*/SKILL.md

Tests to add or update:

• Assert installed files land under .qoder/skills/speckit-<name>/SKILL.md, not .qoder/commands/.
• Assert each SKILL.md contains a name: speckit-<name> frontmatter field.
• Assert uninstall removes the per-skill directories cleanly.
• If a migration path is added, add a test that a project with old .qoder/commands/ files is handled gracefully on reinstall.

Risks & Considerations

• Existing projects break on reinstall: Users who already have .qoder/commands/ files from an older install will need to re-run specify integration install qodercli (or an equivalent migration command) to pick up the new layout. Old files will not be removed automatically unless they are still tracked in the manifest.
• No API breakage in the Python package surface — this is a config/output-path change only.
• Naming change (dotted → hyphenated) is a breaking change for any tooling or scripts that reference the old slash-command names by literal string.

Open Questions

• [NEEDS CLARIFICATION: What is the exact minimum Qoder IDE version that dropped .qoder/commands/ scanning — is it strictly 1.24.0 or was there a minor release before that?]
• [NEEDS CLARIFICATION: Does Qoder IDE 1.24+ still fall back to .qoder/commands/ for older projects, or is the break hard for all versions?]
• [NEEDS CLARIFICATION: Is there an official Qoder migration guide or changelog entry that can be linked in the release notes for this fix?]

---

Posted on behalf of @mnriem by GitHub Copilot (model: claude-sonnet-4.6, autonomous)

Generated by 🐛 Assess Bug from Labeled Issue for issue #4199 · 88.2 AIC · ⌖ 11.1 AIC · ⊞ 34.1K · ◷