qship

Detects repeated prompts across sessions and generates slash command files for recurring rituals.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/QSchlegel/session-viz --skill qship-qschlegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qship
Source: https://github.com/QSchlegel/session-viz/tree/main/plugins/session-viz/skills/qship
Command: npx skills add https://github.com/QSchlegel/session-viz --skill qship-qschlegel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? You keep retyping the same prompts across Claude Code sessions, but not every repeat deserves to become a slash command — some are rituals (procedures you hand-type) and others are misses (prompts that failed and got re-sent). This Skill separates the two and promotes only the genuine rituals into reusable commands. ## Core Features & Use Cases - Ritual vs. Miss Classification: Distinguishes prompts that ran tools successfully (rituals) from prompts that ran nothing and were re-sent (misses), plus mixed cases. - Cross-Session Pooling: Only offers prompts seen in two or more sessions for promotion, so one-off retries within a session are not treated as habits. - Command File Generation: Writes a branch-ready file under .claude/commands/ via --write, refusing to overwrite existing files and never committing on your behalf. - Use Case: You notice you type "ship to preprod" every few days. Run the skill, see it flagged as a ritual across five sessions, and generate a .claude/commands/ file you can edit before committing. ## Quick Start Ask the assistant to run qship and show which of my repeated prompts are worth turning into slash commands.

Frequently Asked Questions about qship

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

FAQPage Schema
How do I turn a repeated prompt into a slash command?▼

Run the qship script to pool repeated prompts across sessions, then use the --write flag with the prompt text to generate a file under .claude/commands/. The file is a starting point you edit and commit yourself.

What is the difference between a ritual and a miss in repeated prompts?▼

A ritual is a repeated prompt where every instance ran tools and drew no correction, meaning you are hand-typing a working procedure. A miss is a repeat where the instance ran no tools, so re-sending just reproduced a no-op.

Why is my repeated prompt not offered for promotion to a command?▼

Only rituals seen in two or more separate sessions are offered for promotion. A repeat within a single session is treated as a retry, not a habit, and misses are never promoted since a command would only make the wrong behavior faster.

Does qship overwrite or commit existing command files?▼

No. The --write flag refuses to overwrite existing files in .claude/commands/, and the skill never commits anything for you. You review and edit the generated file before it lands in your repository.

Can qship rewrite my prompt into a better command wording?▼

No. The skill deliberately preserves exactly what you typed, because the value of the command is that it matches your natural phrasing. A rewritten version would be a different command you would not remember.