remove-superseded-slash-key

Verifies and completes removal of the superseded /key slash command across TUI handlers, modals, docs, and tests.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill remove-superseded-slash-key-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-superseded-slash-key
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/remove-superseded-slash-key
Command: npx skills add https://github.com/catalystctl/catcode --skill remove-superseded-slash-key-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the /key slash command was superseded by /login and /logout, leftover references can linger in TUI handlers, modals, user-facing copy, tests, and docs. This Skill provides a verification checklist to confirm the removal is complete without breaking the wire protocol. ## Core Features & Use Cases - Removal Verification Checklist: Systematically checks TUI slash handlers, command palette, settings hub, and modals for leftover /key references. - Copy and Test Auditing: Ensures auth errors, first-run messages, and smoke tests point users to /login instead of /key, and that obsolete tests are dropped. - Boundary Protection: Explicitly preserves the set_key protocol command, SDK setRuntimeApiKey, and web reauth flows that must not be removed. - Use Case: A maintainer asks whether /key is still needed after /login and /logout exist; this Skill guides confirming the verdict and cleaning up any remaining references. ## Quick Start Ask the agent to verify that the /key slash command was fully removed and fix any leftover references in handlers, docs, and tests.

Frequently Asked Questions about remove-superseded-slash-key

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

FAQPage Schema
How do I remove a deprecated slash command from a TUI application?

Remove the command's case handler from the TUI handler files, delete its entry from the command palette and settings hub, and drop the associated modal functions. Then update user-facing copy and tests to reference the replacement command.

Is the /key command still needed after /login and /logout exist?

No, /key is superseded because /login covers API-key paste, key override, and OAuth, while /logout clears credentials. Only the slash command was removed; the wire set_key protocol command remains for SDK and web reauth.

What should not be removed when deprecating the /key slash command?

Do not remove the protocol set_key command, the SDK setRuntimeApiKey function, or web reauth flows that send set_key. Only the user-facing slash command, its modal, and related tests should be deleted.

How do I verify a command removal is complete in a codebase?

Run ripgrep for patterns like the command's case handler, label, and usage strings such as "/key sk-" or "run /key". The search should return no results outside historical CHANGELOG notes.

Why do auth error messages still mention a removed command?

Leftover user-facing copy in auth errors, first-run prompts, or smoke tests may not have been updated during removal. Audit these strings and change them to direct users to the replacement command like /login.