generate_command

Generate custom slash commands with YAML frontmatter and standardized templates.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill generate-command-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate_command
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/generate_command
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill generate-command-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of creating new custom slash commands by providing a consistent template and clear guidance.

Core Features & Use Cases

  • Standardized command templates ensure every new command follows the same structure and documentation.
  • Frontmatter-driven metadata enforces required fields like name and description for discovery and validation.
  • End-to-end workflow guidance covers planning, implementation steps, testing cues, and repository integration.

Quick Start

Create the command file at .github/commands/generate_command.md following the YAML frontmatter and command template guidelines.

Frequently Asked Questions about generate_command

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

FAQPage Schema
How do I create a custom slash command for a GitHub repository?

To create a custom slash command, generate a markdown file at .github/commands/ with required YAML frontmatter including name and description, followed by a clear command workflow and success criteria.

What is the required structure for GitHub slash command templates?

GitHub slash command templates require YAML frontmatter with name and description fields for discovery and validation, a defined command workflow, success criteria, and optional supporting resources like scripts, references, or assets.

How do I standardize slash commands across multiple repositories and teams?

Standardize slash commands across repositories by applying a consistent template that enforces required metadata validation, file generation, and basic testing conventions for every new command created by different teams.

Does generating a slash command require YAML frontmatter validation?

Yes, slash command generation enforces YAML frontmatter validation requiring both name and description fields to ensure proper command discovery and metadata compliance before the command file is created.

What's the best way to automate new slash command scaffolding with best practices?

Automate slash command scaffolding by using a template-driven approach that applies conventions for frontmatter metadata, workflow steps, testing cues, and repository integration to ensure every command follows best practices.

Can I include supporting scripts and references when I generate a slash command?

Yes, when generating a slash command you can include optional supporting resources such as scripts, references, or assets alongside the required frontmatter, command workflow, and success criteria.