mirror of
https://github.com/github/spec-kit.git
synced 2026-07-03 20:36:23 +08:00
237e918f11
* feat(integrations): add Devin for Terminal skills-based integration - Register DevinIntegration as a SkillsIntegration with .devin/skills/ layout - Add catalog entry, docs row, and supported-agents listing - Display /speckit-<command> hyphen syntax in init "Next Steps" panel (matches Claude/Cursor/Copilot skills mode, since Devin invokes skills by directory name) Closes #2346 * fix(devin): implement -p non-interactive dispatch; clarify skills comment Addresses Copilot review on PR #2364: - Override build_exec_args() in DevinIntegration to emit 'devin -p <prompt> [--model X]' for non-interactive text dispatch (verified Devin CLI supports -p / --print). Returns None when output_json=True since Devin has no structured-output flag, so CommandStep workflows that require JSON cleanly raise NotImplementedError instead of crashing on an unknown CLI flag. requires_cli=True is retained for tool detection. - Extend the skills-integrations enumeration comment in specify_cli/__init__.py to include copilot and devin so the comment matches the code below it. * fix(devin): always return exec args; document plain-text stdout Addresses third Copilot review comment on PR #2364. Returning None from build_exec_args() when output_json=True incorrectly used the codebase's IDE-only sentinel: workflow CommandStep checks 'impl.build_exec_args("test") is None' to detect non-dispatchable integrations (test_workflows.py exercises this with WindsurfIntegration). The previous implementation made Devin appear non-dispatchable to all command steps even though it runs fine via 'devin -p'. Always return the args list. When output_json is requested, Devin is still dispatched and returns plain-text stdout instead of structured JSON; the docstring documents this explicitly. * docs(devin): include claude in skills-integrations enumeration comment Addresses Copilot review on PR #2364: the comment listing skills integrations omitted Claude, which is also a SkillsIntegration subclass. Updated to keep the comment accurate for future readers. * test(devin): add build_exec_args regression tests; bump catalog updated_at Addresses Copilot review on PR #2364, per @mnriem's request to 'address the Copilot feedback, especially the testing ask': - tests/integrations/test_integration_devin.py: add TestDevinBuildExecArgs with three regression assertions: * build_exec_args returns args (not the None IDE-only sentinel) * --output-format is never emitted, regardless of output_json * --model flag is passed through correctly - integrations/catalog.json: bump top-level updated_at to reflect the Devin entry addition so downstream catalog consumers can detect the change reliably.
142 lines
4.4 KiB
YAML
142 lines
4.4 KiB
YAML
name: Agent Request
|
|
description: Request support for a new AI agent/assistant in Spec Kit
|
|
title: "[Agent]: Add support for "
|
|
labels: ["agent-request", "enhancement", "needs-triage"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for requesting a new agent! Before submitting, please check if the agent is already supported.
|
|
|
|
**Currently supported agents**: Claude Code, Gemini CLI, GitHub Copilot, Cursor, Qwen Code, opencode, Codex CLI, Windsurf, Kilo Code, Auggie CLI, Roo Code, CodeBuddy, Qoder CLI, Kiro CLI, Amp, SHAI, Tabnine CLI, Antigravity, IBM Bob, Mistral Vibe, Kimi Code, Trae, Pi Coding Agent, iFlow CLI, Devin for Terminal
|
|
|
|
- type: input
|
|
id: agent-name
|
|
attributes:
|
|
label: Agent Name
|
|
description: What is the name of the AI agent/assistant?
|
|
placeholder: "e.g., SuperCoder AI"
|
|
validations:
|
|
required: true
|
|
|
|
- type: input
|
|
id: website
|
|
attributes:
|
|
label: Official Website
|
|
description: Link to the agent's official website or documentation
|
|
placeholder: "https://..."
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: agent-type
|
|
attributes:
|
|
label: Agent Type
|
|
description: How is the agent accessed?
|
|
options:
|
|
- CLI tool (command-line interface)
|
|
- IDE extension/plugin
|
|
- Both CLI and IDE
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: input
|
|
id: cli-command
|
|
attributes:
|
|
label: CLI Command (if applicable)
|
|
description: What command is used to invoke the agent from terminal?
|
|
placeholder: "e.g., supercode, ai-assistant"
|
|
|
|
- type: input
|
|
id: install-method
|
|
attributes:
|
|
label: Installation Method
|
|
description: How is the agent installed?
|
|
placeholder: "e.g., npm install -g supercode, pip install supercode, IDE marketplace"
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: command-structure
|
|
attributes:
|
|
label: Command/Workflow Structure
|
|
description: How does the agent define custom commands or workflows?
|
|
placeholder: |
|
|
- Command file format (Markdown, YAML, TOML, etc.)
|
|
- Directory location (e.g., .supercode/commands/)
|
|
- Example command file structure
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: argument-pattern
|
|
attributes:
|
|
label: Argument Passing Pattern
|
|
description: How does the agent handle arguments in commands?
|
|
placeholder: |
|
|
e.g., Uses {{args}}, $ARGUMENTS, %ARGS%, or other placeholder format
|
|
Example: "Run test suite with {{args}}"
|
|
|
|
- type: dropdown
|
|
id: popularity
|
|
attributes:
|
|
label: Popularity/Usage
|
|
description: How widely is this agent used?
|
|
options:
|
|
- Widely used (thousands+ of users)
|
|
- Growing adoption (hundreds of users)
|
|
- New/emerging (less than 100 users)
|
|
- Unknown
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: documentation
|
|
attributes:
|
|
label: Documentation Links
|
|
description: Links to relevant documentation for custom commands/workflows
|
|
placeholder: |
|
|
- Command documentation: https://...
|
|
- API/CLI reference: https://...
|
|
- Examples: https://...
|
|
|
|
- type: textarea
|
|
id: use-case
|
|
attributes:
|
|
label: Use Case
|
|
description: Why do you want this agent supported in Spec Kit?
|
|
placeholder: Explain your workflow and how this agent fits into your development process
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: example-command
|
|
attributes:
|
|
label: Example Command File
|
|
description: If possible, provide an example of a command file for this agent
|
|
render: markdown
|
|
placeholder: |
|
|
```toml
|
|
description = "Example command"
|
|
prompt = "Do something with {{args}}"
|
|
```
|
|
|
|
- type: checkboxes
|
|
id: contribution
|
|
attributes:
|
|
label: Contribution
|
|
description: Are you willing to help implement support for this agent?
|
|
options:
|
|
- label: I can help test the integration
|
|
- label: I can provide example command files
|
|
- label: I can help with documentation
|
|
- label: I can submit a pull request for the integration
|
|
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional Context
|
|
description: Any other relevant information about this agent
|
|
placeholder: Screenshots, community links, comparison to existing agents, etc.
|