fix: add slash command hints in workflow completion messages

[CS-Tao]

When artifacts or tasks are complete, the command templates now suggest specific slash commands (/opsx:apply, /opsx:archive) instead of generic guidance, helping users discover the next workflow step.

Summary by CodeRabbit

• Documentation
  • Updated command guidance text to explicitly present available options for users after task completion, providing clearer instructions on next steps.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The /opsx:continue command template in src/core/templates/skill-templates.ts is updated to provide clearer guidance. The final instruction now explicitly presents two options—proceed with /opsx:apply or archive with /opsx:archive—and the success message is rephrased to guide users toward the archive action.

Changes

Cohort / File(s)	Summary
Command Template Messaging src/core/templates/skill-templates.ts	Updated /opsx:continue template guidance text to explicitly offer two distinct action options (/opsx:apply or /opsx:archive) instead of generic continuation language; success output message clarified to direct users toward archiving with /opsx:archive

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat: add slash commands to artifact-experimental-setup #442: Directly introduces the CommandTemplate and getOpsxContinueCommandTemplate that this PR modifies the text content of
• Refine opsx archive sync assessment #514: Performs broader rework of archive/sync prompt wording and action options in the same skill-templates.ts file

Poem

🐰 A rabbit hops through templates bright,
Changing words to guide just right—
"Apply or archive?" now we say,
Clear directions light the way! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding slash command hints to workflow completion messages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Overview

Greptile Summary

Updated workflow completion messages in /opsx:continue and /opsx:apply command templates to include specific slash command hints. The changes replace generic guidance with actionable commands:

• When artifacts are complete: now suggests using /opsx:apply or /opsx:archive
• When tasks are complete: now suggests using /opsx:archive

This improves discoverability by showing users the exact commands to run for the next workflow step.

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The changes are minimal, well-scoped string updates that add specific slash command hints to existing completion messages. The commands referenced (/opsx:apply, /opsx:archive) are valid and widely used throughout the codebase. The backtick formatting is consistent with existing patterns in the file. No logic changes, no security concerns.
• No files require special attention

Important Files Changed

Filename	Overview
src/core/templates/skill-templates.ts	Added specific slash command hints (/opsx:apply, /opsx:archive) to workflow completion messages for better user guidance

Sequence Diagram

sequenceDiagram
    participant User
    participant Agent as Claude Agent
    participant CLI as OpenSpec CLI
    
    Note over User,CLI: Scenario 1: /opsx:continue completion
    
    User->>Agent: /opsx:continue
    Agent->>CLI: openspec status --change "name" --json
    CLI-->>Agent: {isComplete: true, artifacts: [...]}
    Agent->>Agent: Detects all artifacts complete
    Agent->>User: "All artifacts created! You can now implement<br/>this change with `/opsx:apply` or archive<br/>it with `/opsx:archive`."
    
    Note over User,CLI: Scenario 2: /opsx:apply completion
    
    User->>Agent: /opsx:apply
    Agent->>CLI: openspec instructions apply --change "name" --json
    CLI-->>Agent: {tasks: [...], state: "all_done"}
    Agent->>Agent: Implements all tasks
    Agent->>User: "All tasks complete! You can archive<br/>this change with `/opsx:archive`."

Loading

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@src/core/templates/skill-templates.ts`:
- Around line 1954-1955: Update the final user-facing message in
getApplyChangeSkillTemplate() to match the counterpart by replacing "All tasks
complete! Ready to archive this change." with the consistent hint "All tasks
complete! You can archive this change with `/opsx:archive`." Locate the string
inside the getApplyChangeSkillTemplate function and change only the message text
so formatting and punctuation match the other template.
- Around line 1765-1766: The getContinueChangeSkillTemplate() function uses an
older generic success message; update its suggested message string to match the
other template by including the slash command hints—replace the current text
"All artifacts created! You can now implement this change or archive it." with
"All artifacts created! You can now implement this change with `/opsx:apply` or
archive it with `/opsx:archive`." to keep the UX consistent across templates.

[vibe-kanban-cloud]

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.