Help us improve
Share bugs, ideas, or general feedback.
From pulse
Repo-wide or subsystem-wide architecture hygiene pass that surfaces deepening opportunities, shallow modules, leaky seams, and ownership drift. Default mode is report-only: no bead creation or execution unless explicitly requested.
npx claudepluginhub quanpersie2001/pulse --plugin pulseHow this skill is triggered — by the user, by Claude, or both
Slash command
/pulse:architecture-rescueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user wants architecture cleanup that is broader than a single diff: repo-wide, subsystem-wide, or cross-module shape correction.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Guides systematic root-cause debugging via triage checklist for test failures, build breaks, unexpected behavior, logs, and errors.
Share bugs, ideas, or general feedback.
Use this skill when the user wants architecture cleanup that is broader than a single diff: repo-wide, subsystem-wide, or cross-module shape correction.
This skill is for analysis and proposal first. By default it is report-only.
Default to report-only unless the user explicitly asks for planning/execution follow-through.
In report-only mode:
pulse:planningpulse:executingFor the target scope (whole repo or named subsystem), read:
CLAUDE.md, AGENTS.md, and nearby module docs)history/<feature>/CONTEXT.md decisions when present.pulse/memory/* entries that apply to architecture constraints, incidents, or non-regression rulespulse:gitnexus and GitNexus context if availableIf GitNexus is configured, prefer it for topology, process flow, and impact/breadth evidence before manual grep.
Use consistent terms from references/LANGUAGE.md.
Look specifically for:
Use the deletion test: if deleting a module merely moves complexity to callers, it was likely earning leverage; if it removes no real complexity, it was likely shallow or pass-through.
Generate a short list (3-7) of high-signal candidates with concrete evidence.
For each candidate capture:
Return a ranked architecture rescue report:
Do not generate implementation tasks unless asked.
Use only when the user explicitly requests them.
phase-shaping: hand off top approved candidate(s) to pulse:planningexecution-ready: after validating gate approval, proceed via pulse:swarming/pulse:executingBefore leaving report-only mode, restate the mode change and requested scope.
Provide concise output with:
Keep recommendations specific, evidence-backed, and bounded to the requested scope.