ln-015-hex-line-uninstaller
Removes hex-line hooks, output style, and cached files from the system. Use when hex-line MCP needs to be fully uninstalled.
Best use case
ln-015-hex-line-uninstaller is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Removes hex-line hooks, output style, and cached files from the system. Use when hex-line MCP needs to be fully uninstalled.
Teams using ln-015-hex-line-uninstaller should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ln-015-hex-line-uninstaller/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ln-015-hex-line-uninstaller Compares
| Feature / Agent | ln-015-hex-line-uninstaller | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Removes hex-line hooks, output style, and cached files from the system. Use when hex-line MCP needs to be fully uninstalled.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **Paths:** File paths are relative to skills repo root. Locate this SKILL.md directory and go up one level for repo root. # Hex-Line Uninstaller **Type:** L3 Worker **Category:** 0XX Shared Removes all hex-line artifacts from the system. Standalone — no coordinator dependency. --- ## What It Removes | Artifact | Location | Action | |----------|----------|--------| | Hook script | `~/.claude/hex-line/hook.mjs` | Delete file | | Hook entries | `~/.claude/settings.json` → `hooks` | Remove entries matching "hex-line" signature | | Output style file | `~/.claude/output-styles/hex-line.md` | Delete file | | Output style setting | `~/.claude/settings.json` → `outputStyle` | Clear only if value is `"hex-line"` | | Hook directory | `~/.claude/hex-line/` | Delete if empty after hook removal | --- ## Steps ### 1. Remove hook entries from settings.json ``` Read ~/.claude/settings.json For each event in hooks (SessionStart, PreToolUse, PostToolUse): Find entry where hooks[].command contains "hex-line" Remove that entry If event array is empty, delete the key If hooks object is empty, delete it Write back ``` ### 2. Clear output style ``` If settings.json.outputStyle === "hex-line": Delete the outputStyle key Write back ``` ### 3. Delete installed files ```bash rm -f ~/.claude/hex-line/hook.mjs rmdir ~/.claude/hex-line 2>/dev/null # only if empty rm -f ~/.claude/output-styles/hex-line.md ``` ### 4. Verify ```bash # Confirm no hex-line references remain grep -r "hex-line" ~/.claude/settings.json || echo "Clean" test ! -f ~/.claude/hex-line/hook.mjs && echo "Hook removed" test ! -f ~/.claude/output-styles/hex-line.md && echo "Style removed" ``` --- ## Notes - Does NOT remove the MCP server itself (`npm uninstall -g @levnikolaevich/hex-line-mcp` is separate) - Does NOT touch per-project `.claude/settings.local.json` (autoSync already cleans those) - Safe to run multiple times (idempotent) - After uninstall, restart Claude Code for changes to take effect ## Definition of Done - [ ] No hex-line entries in `~/.claude/settings.json` hooks - [ ] No `outputStyle: "hex-line"` in settings (unless user re-set it) - [ ] `~/.claude/hex-line/hook.mjs` does not exist - [ ] `~/.claude/output-styles/hex-line.md` does not exist **Version:** 1.0.0 **Last Updated:** 2026-03-27
Related Skills
ln-1000-pipeline-orchestrator
Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.
ln-100-documents-pipeline
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
ln-914-community-responder
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.
ln-913-community-debater
Launches RFC and debate discussions on GitHub. Use when proposing changes that need community input or voting.
ln-912-community-announcer
Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.
ln-911-github-triager
Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.
ln-910-community-engagement
Analyzes community health and delegates engagement tasks. Use when managing GitHub issues, discussions, and announcements.
ln-840-benchmark-compare
Runs built-in vs hex-line benchmark with scenario manifests, activation checks, and diff-based correctness. Use when measuring hex-line MCP performance against built-in tools.
ln-832-bundle-optimizer
Reduces JS/TS bundle size via tree-shaking, code splitting, and unused dependency removal. Use when optimizing frontend bundle size.
ln-831-oss-replacer
Replaces custom modules with OSS packages using atomic keep/discard testing. Use when migrating custom code to established libraries.
ln-830-code-modernization-coordinator
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
ln-823-pip-upgrader
Upgrades Python pip/poetry/pipenv dependencies with breaking change handling. Use when updating Python dependencies.