All authors

Claude Skills by shortcuts
github.com/shortcuts17 skills0 installs13 views
- DocumentationCreates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize...Votes: 0GitHub stars: 18
- ExplainExplain any topic as one illustrated Obsidian note in the spirit of The Way Things Work - the principle, the machine opened up, and trusted sources to go further.Votes: 0GitHub stars: 18
- No Ai SlopEdit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.Votes: 0GitHub stars: 18
- Release NotesGenerate user-facing release notes from tickets, PRDs, git logs, or internal changelogs. Use when writing release notes, creating a changelog, announcing a product update, or summarizing what shipped.Votes: 0GitHub stars: 18
- Self ReviewSummarize what the user shipped on GitHub over a time range, as one Obsidian note with one subsection per system. Use whenever the user asks what they accomplished or shipped over a period - "what did I do since last november", "self review", "write my perf review", "recap my last quarter" - including when they never say "self review" or name a repository.Votes: 0GitHub stars: 18
- OnboardOnboard an engineer on a repository, directory, feature, or function with one zoomable HTML map - the stack, each package's role, how the data flows, and links to the code.Votes: 0GitHub stars: 18
- Test AuditInvoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.Votes: 0GitHub stars: 18
- Radin DoctorCheck that radin's install under ~/.claude is complete and its companion tools are reachable.Votes: 0GitHub stars: 5
- Radin PlanWrite an implementation plan for one backlog entry, touching no code. Use for /radin-plan, "plan this backlog entry", "write a plan for X before we execute it". Scope is one task, not the whole backlog.Votes: 0GitHub stars: 5
- Radin RecordLog bugs, follow-ups, ideas or feedback raised this session as backlog entries that outlive the conversation. Use for /radin-record or any ask to save something for later, even a vague one ("add the findings"): scan the whole session.Votes: 0GitHub stars: 5
- Radin ReviewReview a commit, PR, directory or range on two axes, Standards (repo rubrics) and Spec (the originating backlog entry), triage findings with the user, and log the kept ones as backlog entries. Use for /radin-review, "review and log to backlog".Votes: 0GitHub stars: 5
- Radin Setup HooksWire codebase-memory-mcp into this repo when install.sh could not do it globally. Use for "set up hooks", "wire up codebase-memory-mcp", "enable the knowledge graph here", or when the graph's MCP tools are missing in a project.Votes: 0GitHub stars: 5
- Radin ShowPrint the current project's backlog to the terminal.Votes: 0GitHub stars: 5
- Radin StatsShow the stats/gain output of every companion tool that ships one, side by side.Votes: 0GitHub stars: 5
- Radin UninstallRemove everything install.sh copied into ~/.claude: radin's skills and lib scripts.Votes: 0GitHub stars: 5
- Radin ExecuteWork through the whole backlog with a planning pass: prioritize every task, plan and execute each via a sub-agent, commit after each. Use for "work through my backlog", not one named task. Asks the user when an entry is ambiguous.Votes: 0GitHub stars: 5
- Radin ImplementWork through the whole backlog with no planning pass: prioritize every task, implement each straight from its entry via a sub-agent, commit after each. Use for "skip planning", "just implement the backlog". A task with a plan still follows it.Votes: 0GitHub stars: 5