convert-custom-slash-for-codex

Convert Claude Command to Codex Prompt

You are tasked with converting a Claude custom slash command from .claude/commands/ to Codex-optimized prompt format for .codex/prompts/.

Parameter

• COMMAND_NAME (required): Name of the Claude command to convert (without .md extension)
  • Example: fix-issue
  • Example: fix-linter
  • Usage: /convert-custom-slash-for-codex fix-issue

Context

This repository uses both Claude (via .claude/commands/) and Codex (via .codex/prompts/). Codex prompts require:

1. YAML frontmatter with description: and argument-hint: fields
2. Placeholder syntax ($1, $2, $ARGUMENTS, $NAMED_PARAM) instead of markdown parameter references
3. Literal dollar signs using $$ syntax

Conversion Process

Step 1: Validate Input

1. Check that COMMAND_NAME parameter is provided
2. Verify source file exists: .claude/commands/$COMMAND_NAME.md
3. If file doesn't exist, report error and list available commands

Step 2: Read Source Command

1. Read the entire content from .claude/commands/$COMMAND_NAME.md
2. Store the original content for conversion

Step 3: Extract Metadata

Description

• Extract from the first heading (without # symbols)
• If heading contains parameter placeholders, keep them for now (will convert later)
• Limit to 100-150 characters for Codex menu display
• Example: # Fix Issue #{issue_number} → Description: Fix Issue #{issue_number}

Argument Hints

Analyze the command content for parameter patterns:

Common Parameter Patterns:

• #{issue_number} or {issue_number} → ISSUE_NUMBER=#123
• #{pr_number} or {pr_number} → PR_NUMBER=#456
• {file_path} → FILE_PATH=<path>
• {name} or {description} → NAME=<value> or DESCRIPTION=<value>

Argument Hint Format:

• Single parameter: ISSUE_NUMBER=#123
• Multiple parameters: ISSUE_NUMBER=#123 PR_NUMBER=#456
• Optional parameters: [PARAM=<value>] (use square brackets)
• Required parameters: PARAM=<value> (no brackets)