slash-commands

Define explicit slash commands that encapsulate multi-step workflows.

25|3|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill slash-commands-nimadorostkar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slash-commands
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/agent-tooling/slash-commands
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill slash-commands-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of retyping repetitive prompts and ensures consistent execution of multi-step workflows by turning them into explicit, user-triggered commands.

Core Features & Use Cases

  • Workflow Standardization: Encapsulates complex, multi-step processes like code reviews or release management into a single, repeatable command.
  • Context Pre-gathering: Uses shell execution to gather necessary data (diffs, logs, status) before the model even begins processing, saving significant time and tool-call overhead.
  • Use Case: Instead of manually gathering git logs, diffs, and CI status for a code review, you can invoke a custom /review command that automatically compiles all required context for the agent.

Quick Start

Define a new slash command by creating a markdown file that specifies the workflow steps and uses the ! prefix to execute shell commands for context gathering.

Frequently Asked Questions about slash-commands

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

FAQPage Schema
How do I automate recurring agent workflows and stop retyping repetitive prompts?▼

You can automate recurring agent workflows by defining explicit, user-invoked slash commands that encapsulate multi-step tasks into reusable automation. This eliminates friction by turning complex processes into a single, repeatable command.

How does shell execution pre-gather context for agent workflows?▼

Shell execution pre-gathers context by using the ! prefix to run shell commands for data collection, such as git diffs, logs, and status, before the model begins processing. This saves significant time and tool-call overhead.

What's the best way to standardize complex code reviews using agent tooling?▼

Standardize complex code reviews by creating a custom slash command that automatically compiles required context like git logs and CI status. This encapsulates the entire multi-step review process into a single, repeatable command.

How do I define a new slash command for project-level automation?▼

Define a new slash command by creating a markdown file that specifies the workflow steps and uses the ! prefix to execute shell commands for context gathering. This facilitates reusable automation for project-level, personal, or plugin-based operations.

What security precautions are needed when enabling shell execution for automated workflows?▼

When enabling shell execution for automated workflows, you must carefully scope allowed tools and shell execution to ensure secure and efficient context gathering. Proper scoping prevents unauthorized actions during multi-step task automation.

Can I use slash commands for personal automation tasks or are they limited to project-level operations?▼

You can use slash commands for both personal and project-level operations, as well as plugin-based operations. The system facilitates the creation of reusable automation across all these scopes without limitation.