regenrek

Implement remaining scoped work in this repository to verified completion. Use for direct bug fixes, regressions, failing tests, `planr-review` findings, or unfinished `.planr` plan phases when the next step is to change code, tests, or docs, keep live `.planr` status honest, and prove the result. Not for writing a new execution contract (`planr-plan`), giving a verdict-only status answer (`planr-status`), or running a findings-first audit (`planr-review`).

Create or update executable `.planr/plans/*.plan.md` contracts in this repository. Use when scope, ownership, phase breakdown, verification, or acceptance criteria must be defined before implementation, including bug-to-plan conversions and review-finding follow-up plans. Not for executing fixes (`planr-fix`), giving a verdict-only status answer (`planr-status`), or running a findings-first audit (`planr-review`).

Review agent-owned implementation scope in this repository against `.planr` plans or live status, path-scoped Git evidence, and acceptance criteria. Use for findings-first audits of completion, correctness, architecture, hard-cut cleanup, and test sufficiency. Not for implementing fixes (`planr-fix`), writing a new execution contract (`planr-plan`), or giving a verdict-only status answer (`planr-status`).

Assess the honest current state of a scoped `.planr` task in this repository. Use when the user asks what is done, what remains, what is blocked, whether a scope is complete, which scopes are open, or what should come next. Start with the deterministic `.planr` CLI where it has command coverage. Not for implementing fixes (`planr-fix`) or running a findings-first audit (`planr-review`).

Produce a user-facing recap of an owned `.planr` scope in this repository. Use when the user asks what changed, why it changed, what works now, what intentionally no longer works, or what remains blocked after `planr-fix`, `planr-status`, or `planr-review`. Not for deciding completion (`planr-status`), running a findings-first audit (`planr-review`), or continuing implementation (`planr-fix`).

Traces failures from observed symptoms to the first incorrect state transition.

Reviews TypeScript and agent workflow changes with strict risk focus.

__PLUGIN_DESCRIPTION__. Use when [describe trigger scenarios].

Automate npm Trusted Publisher setup via the npm-trustme CLI. Use when configuring or verifying npm Trusted Publishers for GitHub Actions with npx npm-trustme, including browser automation and WebAuthn passkey approval.

Release automation for npm-trustme. Use when asked to cut a new npm-trustme version, run the release script, or tag/publish a new release.

Capture and analyze thread backtraces with LLDB/GDB to debug hangs, deadlocks, UI freezes, IPC stalls, or high-CPU loops across any language or project. Use when an app becomes unresponsive, switching contexts stalls, or you need thread stacks to locate lock inversion or blocking calls.

Use when operating peky from the CLI or TUI, especially for AI agents who need reliable, low-error procedures. Covers how to target sessions/panes correctly, use scopes, avoid confirmation prompts, and keep CLI/TUI/daemon in sync.

Control Samsung TVs via SmartThings (OAuth app + device control).