Add slash command substitution to codingcontext package

[Copilot]

Move slash command code into main package ✅

Summary

Successfully implemented slash command functionality in the main codingcontext package. Slash command parsing is always enabled - no flag needed. When a task contains a slash command (even in parameter values or with leading formatting), it fully replaces both the task name and all parameters.

All Tasks Complete ✅

• Move slash command parsing code from pkg/slashcommand to pkg/codingcontext
• Update Context.Run() to always check for slash commands in task content
• When slash command is found:
  • Extract task name and parameters from slash command
  • Completely replace task name and all parameters (not merge)
  • Always reload task file, even if same task name
  • Improved logging: "Reloading" vs "Switching" based on task name
• Expand parameters before slash command check - enables slash commands in parameter values
• Support leading periods and spaces - works with markdown formatting like . /taskname
• Add comprehensive tests for slash command functionality
• Refactored code to eliminate duplication
• Added clarifying comments for code review feedback
• Merged with main branch - resolved conflicts, compatible with agent targeting functionality
• Run linting, building, and testing - all passing ✅
• Update documentation to reflect full replacement behavior
• Code review completed and all feedback addressed
• Security scan completed - no vulnerabilities found ✅

How It Works

Basic slash command:

# wrapper.md contains: /fix-bug 123 "critical issue"
coding-context wrapper
# Switches to fix-bug task with params: $1=123, $2="critical issue"

Free-text use case (slash command in parameter value):

# free-text.md contains: ${text}
coding-context -p text="/fix-bug PROJ-123" free-text
# 1. Expands ${text} to "/fix-bug PROJ-123"
# 2. Detects slash command and switches to fix-bug task
# 3. Sets new parameters: $1=PROJ-123
# 4. Expands fix-bug task content with new parameters

Slash command with leading formatting (markdown, bullet points, etc.):

# wrapper.md contains: .   /fix-bug PROJ-456
coding-context wrapper
# Detects slash command even with leading period and spaces
# Switches to fix-bug task with $1=PROJ-456

The slash command fully replaces both the task name and ALL parameters!

Final Testing Results

✅ All unit tests passing (16 test cases including slash command and agent tests)
✅ All integration tests passing
✅ Linting passing with no errors
✅ Manual testing verified all scenarios including . /taskname patterns
✅ Code review feedback fully addressed
✅ Merged with main branch successfully
✅ Security scan - no vulnerabilities found

Backward Compatibility

The original pkg/slashcommand package remains unchanged for backward compatibility. Slash commands now work automatically with:

• Parameter expansion support
• Leading formatting support (periods, spaces)
• Full task and parameter replacement
• Compatible with new agent targeting functionality from main (both -a and -t flags coexist)

Original prompt

Move the "slash command" code into the main package. The user should be given a WithSlashCommand(bool) option. When this is provided, if the found task contains a slash command, then that should be substituted.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[alexec]

@copilot Make it -l

[Copilot]

@copilot Make it -l

Changed to -l in commit bdee632. Also updated to always reload the task file even when the slash command references the same task name (e.g., /free-text).

[alexec]

@copilot Remove the "WithSlackCommand" option and just default to true..

[Copilot]

@copilot Remove the "WithSlackCommand" option and just default to true..

Removed WithSlashCommand option and -l flag in commit 91d9206. Slash command parsing is now always enabled by default - no configuration needed.

[alexec]

@copilot Try again

[Copilot]

@copilot Try again

Fixed in commit c59b07b. Now expands parameters before checking for slash commands, enabling the free-text use case where coding-context -p text="/fix-bug PROJ-123" free-text works correctly.

[alexec]

@copilot We should support

"/taskname"
". /taskname"
". /taskname
"

[Copilot]

@copilot We should support

"/taskname"...

Already supported by the existing implementation. Added explicit test cases in commit 91798f1 to document and test patterns like . /taskname, . /taskname, and with arguments.

[alexec]

@copilot What about if there are no arguments and the end of the taskname is the end of the string?

[Copilot]

@copilot What about if there are no arguments and the end of the taskname is the end of the string?

Already handled correctly. When no whitespace is found after the slash (line 50-53 in slashcommand.go), the entire remaining string becomes the task name with empty params. Existing tests cover this: /fix-bug, . /taskname, and . /taskname all work correctly with no arguments.

[alexec]

@copilot fetch main and resolve conflicts.

[Copilot]

@copilot fetch main and resolve conflicts.

Merged origin/main in commit 853f2bd. Resolved conflicts by keeping both -a (agent) and -t (frontmatter) flags, and both test functions. All tests passing.