dotfiles

Log feedback, bugs, follow-ups, or ideas raised mid-session as structured BACKLOG.md entries, so they survive past the conversation. Use for /radin-record, "log this to BACKLOG.md", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks ("add the findings") — scan the whole session, not just the literal text.

Run a thermo-nuclear code quality review over a scope (commit, PR, directory, or a range like "since yesterday") and log each finding as a BACKLOG.md entry instead of printing to terminal. Use for /radin-review, "review and log to backlog", "audit this commit/PR/directory and file backlog entries", "turn this review into a backlog".

Wire up per-repo hooks/MCP config for radin's companion tools (code-review-graph). Use for "set up hooks", "wire up code-review-graph", "enable the knowledge graph here", or right after install.sh in a new project.

Refresh radin's agents/skills in ~/.claude/ by re-running install.sh (latest release or main), overwriting what's there. Use for "update radin", "pull the latest radin", "reinstall radin", /radin-update.

Audit a feature branch against origin/main to highlight changes, verify test coverage, and detect potential bugs. Use this skill whenever you need to: - Understand what changed in a branch compared to main - Verify all changes have corresponding unit tests - Detect potential bugs or regressions - Assess merge risk and readiness - Review code quality, formatting, and architecture - Get actionable recommendations for test coverage gaps This is pgpemu-specific: It understands the ESP32-C3 firmware architecture, the comprehensive test suite (252 assertions across 8 test modules), and code review standards from AGENTS.md. The auditor scans the entire codebase—no specificity needed, the unit tests handle verification.

Reformat messy Obsidian web-clip documents into clean, standardized markdown. Use this skill when you need to clean up web clips, remove website navigation cruft, strip HTML tags, embed images with context, generate concise titles, add meaningful tags, or transform cluttered documents into readable notes. Handles Reddit posts, blog articles, and other web content. Trigger phrases include "format Obsidian document", "clean up web clip", "remove HTML from markdown", "fix messy note", "standardize web clippings", "embed images", "generate better title".

Audit the main branch to determine if the repository is ready for a new release. Runs build/lint/test checks, audits documentation consistency against changes since the last release, and logs every failure to ISSUES.md. Returns a clear go/no-go verdict. Use this skill whenever the user wants to: - Check if the codebase is release-ready - Run a pre-release audit or checklist - Validate that docs are in sync with code changes - Get a release go/no-go verdict before tagging - Run "release checks", "pre-release audit", "is this ready to ship?"

Explain the why and how of a git commit or pull request as a single, terse HTML page.

Summarize a PR or branch into a concise, non-technical notebook entry with "What we did" and "Expected outcome" sections. Aimed at engineering managers and executives. Use when the user wants a PR summary, branch summary, notebook entry, exec summary, or non-technical report.