Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
full-statck-skills avatar

Speckit Check

  • 5 installs
  • Updated July 29, 2026
  • full-statck-skills/speckit-skills

Runs `specify check` to verify that Spec Kit's required tools (git, AI agents, editors) are installed and detectable.

About

Runs the Specify CLI environment check and interprets which tools are present or missing. A developer uses it after setup or when slash commands do not appear.

  • Reports detected AI agents and editors
  • Suggests concrete fixes for missing tools or PATH issues

Speckit Check by the numbers

  • 5 all-time installs (skills.sh)
  • Ranked #424 of 550 CLI & Terminal skills by installs in the Skillselion catalog
  • Data as of Jul 30, 2026 (Skillselion catalog sync)
npx skills add https://github.com/full-statck-skills/speckit-skills --skill speckit-check

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs5
Last updatedJuly 29, 2026
Repositoryfull-statck-skills/speckit-skills

What it does

Runs `specify check` to verify that Spec Kit's required tools (git, AI agents, editors) are installed and detectable.

Files

SKILL.mdMarkdownGitHub ↗

Spec Kit Check Skill

Run specify check to verify that the Spec Kit CLI and required tools (git, AI agents, editors) are installed and detectable. Use this after speckit-install or speckit-initial to confirm the environment, or when the user reports that slash commands are missing or specify does not work.

When to Use

  • After initializing a project with speckit-initial to confirm the environment.
  • When slash commands do not appear or the user says "specify not working".
  • In CI or scripts to ensure dependencies are present before running Spec Kit steps.

Prerequisites

  • Specify CLI must be installed (see speckit-install). If specify is not in PATH, direct the user to speckit-install before running specify check.

Workflow

1. Ensure CLI is available

  • If the user has not installed the CLI or reports "specify: command not found", direct them to speckit-install first. Do not run specify check until specify is available.

2. Run the check

  • From the project root (or target directory): specify check
  • The command reports which tools are detected (e.g. git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder) and which are missing or not in PATH.

3. Interpret the output

  • All required tools present: Environment is ready; suggest proceeding with speckit-constitution or speckit-specify.
  • CLI missing: Direct to speckit-install.
  • Agent or editor missing: Suggest installing the corresponding Agent/editor or adding its executable to PATH. If the user only needs templates and .specify/ (no slash commands), suggest re-running speckit-initial with --ignore-agent-tools.

4. Summarize and recommend

  • Provide a short summary: what is OK, what is missing.
  • Give concrete next steps: install CLI (speckit-install), re-init with different agent (speckit-initial), or fix PATH / install Agent.

Outputs

  • Summary: Which tools are detected and which are missing.
  • Recommendations: List of next actions (install CLI, run init, install Agent, add to PATH, or use specify init --ignore-agent-tools).

Next Steps

  • If something is missing: use speckit-install (for CLI) or speckit-initial (to re-init or use --ignore-agent-tools), or install the missing Agent/editor.
  • If check passes: proceed with speckit-constitution or speckit-specify.

Example Output (reference)

See examples/sample-output.md for an example of specify check output and how to interpret it.

Troubleshooting

  • "specify: command not found": Use speckit-install.
  • Agent reported as missing: Ensure the Agent app is installed and its CLI or executable is on PATH; or use specify init --ignore-agent-tools if only templates are needed.
  • Git missing: Install git or run specify init --no-git if git is not required for the workflow.

References

国内适配

  • 支持中文文档和中文注释
  • 示例代码兼容国内开发环境
  • 提供中文 FAQ 和常见问题解答

能力边界

✅ 适用场景

  • 当你需要使用此技能对应的技术栈时
  • 当项目需要遵循最佳实践时
  • 当需要快速上手或深入理解核心概念时

⚠️ 需要注意

  • 复杂业务逻辑需要结合具体场景调整
  • 性能优化需要根据实际数据量评估

❌ 不适用场景

  • 不相关的技术栈或框架
  • 需要完全自定义的特殊场景

使用流程

Step 1: 环境准备

确保开发环境已安装必要的依赖和工具。

Step 2: 配置初始化

根据项目需求进行基础配置。

Step 3: 核心功能使用

按照示例代码实现核心功能。

Step 4: 测试验证

运行测试确保功能正常。

Step 5: 部署上线

完成开发后进行部署和监控。

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.