edit-command

Automate Claude Code slash command lifecycle with YAML frontmatter validation.

19|5|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/digital-stoic-org/agent-skills --skill edit-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-command
Source: https://github.com/digital-stoic-org/agent-skills/tree/main/dstoic/skills/edit-command
Command: npx skills add https://github.com/digital-stoic-org/agent-skills --skill edit-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create, update, and optimize Claude Code slash commands with safe defaults and structured frontmatter.

Core Features & Use Cases

  • Frontmatter-driven command definition: name, description, model, and allowed-tools.
  • Safe editing workflow: perform surgical updates to existing commands and validate frontmatter.
  • Discoverability and reuse: ensures commands are easily discoverable across teams and projects.

Quick Start

Create or update a slash command by adding or editing a Markdown file with frontmatter in the appropriate commands directory.

Frequently Asked Questions about edit-command

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

FAQPage Schema
How do I create Claude Code slash commands with YAML frontmatter?

To create Claude Code slash commands, you add or edit a Markdown file with YAML frontmatter in the appropriate commands directory, defining the name, description, model, and allowed-tools to ensure discoverability across projects.

What is the best way to update existing slash commands safely?

The best way to update existing slash commands safely is through a surgical editing workflow that validates the YAML frontmatter and enforces safe defaults for argument patterns, model selection, and tool usage.

Can I define allowed tools and model selection when authoring slash commands?

Yes, you can define allowed tools and model selection within the YAML frontmatter of your command Markdown files, ensuring structured definition and safe tool usage for your team.

Why do I need structured frontmatter for custom Claude Code commands?

Structured YAML frontmatter is required for custom Claude Code commands to enforce required fields, support argument patterns, and ensure commands are easily discoverable and reusable across teams and projects.

Does this approach work for teams managing slash commands across multiple projects?

Yes, this approach is designed for teams that author, audit, and evolve internal commands across multiple projects, automating the command lifecycle and enforcing consistent frontmatter validation.

What are the limitations when modifying slash command Markdown files?

When modifying slash command Markdown files, you are constrained by the required YAML frontmatter fields and safe defaults, meaning updates must strictly adhere to the enforced structure for argument patterns and tool usage.