Qcommand-creator

Create Claude Code slash commands with standardized SKILL.md structure.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qcommand-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Qcommand-creator
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qcommand-creator
Command: npx skills add https://github.com/inho-team/qe-framework --skill qcommand-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating Claude Code slash commands can be repetitive and error-prone. This skill guides you to define a command once and reuse it consistently across projects or teams.

Core Features & Use Cases

  • Guidance to determine whether a command should live at the project level (.claude/commands/) or at the global/user level (~/.claude/commands/).
  • Access to standardized command patterns (Workflow Automation, Iterative Fixing, Agent Delegation, Simple Execution) and best practices for naming, arguments, and workflow steps.
  • Auto-generation of an optimized command file ready for version control and deployment, with a clear path to testing.

Quick Start

Ask the assistant to create a new slash command by providing its name, purpose, and desired pattern; the system will generate an optimized command file in the correct location.

Frequently Asked Questions about Qcommand-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate multi-step workflows with Claude Code slash commands?

You can automate multi-step workflows by defining a slash command once with a specific pattern like Workflow Automation or Agent Delegation, then reusing it consistently across Claude Code projects to standardize repetitive tasks.

How do I create a custom slash command for Claude Code?

To create a custom slash command, provide its name, purpose, and desired pattern to the assistant, which then generates an optimized command file with structured SKILL.md frontmatter in the correct .claude/commands/ directory.

What is the best way to structure Claude Code project commands versus global commands?

Project commands should live in the local .claude/commands/ directory for specific workflows, while global commands reside in ~/.claude/commands/ to standardize reusable automation across all your projects.

What patterns are available for standardizing Claude Code command templates?

Available patterns include Workflow Automation, Iterative Fixing, Agent Delegation, and Simple Execution, providing standardized structures for naming, arguments, and defining multi-step workflow logic.

Does Claude Code command automation support version control deployment?

Yes, the automation process auto-generates an optimized command file ready for version control and deployment, providing a clear path for testing within your established development workflows.

Why do I need structured frontmatter in Claude Code slash commands?

Structured frontmatter is required to satisfy creation requirements and align with best practices, ensuring the command integrates properly with Claude Code and executes the intended automation reliably.