[Agent]: Add support for Nexora Code #5315

Agent Name

Nexora Code

Official Website

https://marketplace.visualstudio.com/items?itemName=nexora-intelligence.nexora-code (editor extension, also on Open VSX) · CLI: https://www.npmjs.com/package/@nexoracode/cli

Agent Type

Both CLI and IDE

CLI Command (if applicable)

nexora (optional companion to the editor extension)

Installation Method

IDE marketplace (VS Code Marketplace / Open VSX: nexora-intelligence.nexora-code); CLI: npm i -g @nexoracode/cli

Command/Workflow Structure

Skills-style. A skill is a directory with a SKILL.md (YAML frontmatter: name, description, optional argument-hint; body = instructions). Nexora Code and the CLI read .nexora/skills/<name>/SKILL.md (project) and ~/.nexora/skills/ (user), plus the shared .agents/skills/ root. Any installed skill is invocable as /<name> [args], so Spec Kit commands are /speckit-specify, /speckit-bug-assess, etc. (dash separator, like the Copilot/Claude skills layouts).

Argument Passing Pattern

$ARGUMENTS in the skill body is replaced literally by whatever follows the command (single-pass, no shell interpolation); when the body has no placeholder the text is appended as the task.

Popularity/Usage

New/emerging (less than 100 users)

Documentation Links

• Nexora Code Spec Kit guide: https://github.com/Nexora-Intelligence/nexora-vscode/blob/main/docs/spec-kit.md
• Skills format: https://github.com/Nexora-Intelligence/nexora-vscode/blob/main/README.md

Use Case

Nexora Code 1.14.0 and the nexora CLI 1.10.0 run the three Spec Kit processes natively (SDD, bug triage, idea assessment) with bundled, pinned copies of the Spec Kit templates and command prompts, and prefer a project's own .specify/ and installed speckit-* skills when present. A first-class nexora integration lets specify init --integration nexora (and specify extension add bug|assess) install the commands where Nexora reads them, so a team that already uses Spec Kit with another agent gets the same /speckit-* surface in Nexora without any manual copying.

Example Command File

---
name: speckit-specify
description: Create or update the feature specification from a natural language feature description.
argument-hint: "<feature description>"
---
<!-- Source: speckit -->
... (the rendered body of templates/commands/specify.md with $ARGUMENTS)

Contribution

• I can help test the integration
• I can provide example command files
• I can help with documentation
• I can submit a pull request for the integration

Additional Context

An implementation is ready: a SkillsIntegration (key = "nexora", folder .nexora/, skills under .nexora/skills, hyphen separator, multi_install_safe, requires_cli = False, argument hints as in the Claude integration), docs/integrations/nexora.md, catalog/index/registry entries and tests (74 integration tests; full suite green apart from one pre-existing PowerShell-parity test that needs pwsh). End-to-end: specify init --integration nexora + extension add bug + extension add assess writes 17 .nexora/skills/speckit-*/SKILL.md. I will open a draft pull request from a fork referencing this issue so it can be reviewed against the integration contribution guidance; happy to turn it into an external adapter + catalog listing instead if that is the preferred path for a new agent.

AI Disclosure

Drafted with AI assistance (Claude Code, Claude Fable 5.1) under my direction; I reviewed the implementation, ran the test suite and the end-to-end check locally, and take responsibility for the submission.