From claude-code-dev
Copies commands from Product Forge plugins to user (~/.claude/) or project (.claude/) directories. Lists available plugin:command options without arguments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-dev:copy-commandThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Copy a command from Product Forge plugins to your user-level (`~/.claude/`) or project-level (`.claude/`) directory.
Copy a command from Product Forge plugins to your user-level (~/.claude/) or project-level (.claude/) directory.
# List available commands
/copy-command
# Copy to project (default)
/copy-command product-design:create-prd
# Copy to user level
/copy-command git-workflow:commit --user
# Explicit project level
/copy-command devops-data:create-rfc --project
<plugin>:<command-name> - The command to copy in plugin:name format--user - Copy to ~/.claude/{plugin}/commands/{name}.md--project - Copy to .claude/{plugin}/commands/{name}.md (default)Commands are single markdown files (.md) containing:
# Project-level (default)
.claude/
└── git-workflow/
└── commands/
└── commit.md
# User-level (--user)
~/.claude/
└── git-workflow/
└── commands/
└── commit.md
When the user runs this command:
Scan Product Forge plugins cache for all available commands:
ls ~/.claude/plugins/cache/product-forge-marketplace/*/commands/*.md 2>/dev/null
For each plugin with commands, list them with descriptions:
description{plugin}:{command-name} - {description}Display formatted list:
Available commands from Product Forge:
product-design:
create-prd - Interactive PRD creation wizard
create-qa-test - Create a new QA test procedure
task-focus - Focus on a specific task with context
...
git-workflow:
commit - Guided git commit with atomic commit analysis
rebase - Rebase local changes on remote updates
code-review - Review code changes for issues
...
devops-data:
create-rfc - Create a new RFC technical specification
create-tech-spec - Create a new Technical Specification
...
Usage: /copy-command <plugin>:<command-name> [--user | --project]
Parse arguments:
plugin and command-name from <plugin>:<command-name> format--user or --project (default)Locate source command:
SOURCE=~/.claude/plugins/cache/product-forge-marketplace/{plugin}/commands/{command-name}.md
Determine destination path:
--project: .claude/{plugin}/commands/{command-name}.md--user: ~/.claude/{plugin}/commands/{command-name}.mdCheck if destination exists:
Command '{command-name}' already exists at {destination}.
Options:
- Overwrite: Replace existing command
- Rename: Save as {command-name}-copy.md
- Cancel: Abort operation
Create destination directory structure:
mkdir -p {destination_dir}
Copy command file:
cp {source} {destination}
Confirm success:
Command copied successfully!
Source: ~/.claude/plugins/cache/product-forge-marketplace/{plugin}/commands/{command-name}.md
Destination: {destination}
The command is now available as /{command-name} in your {project|user} configuration.
npx claudepluginhub jpoutrin/product-forge --plugin claude-code-devGuides developers on creating, structuring, and organizing slash commands for Claude Code. Covers YAML frontmatter, dynamic arguments, bash execution, user interactions, and best practices for reusable command workflows.
Guides creating slash commands for Claude Code: structure, YAML frontmatter, dynamic arguments, file references, bash execution, user interactions, organization, and best practices.
Guides creation of legacy slash commands for Claude Code (.claude/commands/ format), including YAML frontmatter, dynamic args, bash execution, git integration, and user interaction patterns.