All authors
Claude Skills by philoserf
github.com/philoserf13 skills0 installs8 views
- Cc Release ReviewReviews Claude Code release notes and recommends config updates. Use when asking "what changed in the CLI/release", "what should I update", or "review the latest release". Covers settings.json, hooks, permissions, rules, skills, and CLAUDE.md.Votes: 0GitHub stars: 13
- Code AuditReviews a codebase for bugs, design issues, and code cleanliness problems with specific file paths and line numbers. Use when auditing code quality, finding bugs, doing a code review, or reviewing a project for issues. Writes issues to `.issues/`.Votes: 0GitHub stars: 13
- EditorCopy edits prose while preserving voice and register. Use when asked to edit, copy edit, proofread, revise, polish, tighten, or rewrite essays, articles, drafts, or fiction. Flags wordiness, passive voice, clichés, hedging, and nominalizations.Votes: 0GitHub stars: 13
- Code ReductionReviews a codebase for what to delete, inline, and flatten — abstractions that don't earn their keep, ceremonial types, obscuring indirection, tests of language features. Use when code has accreted structure and needs shrinking. Writes findings to `.issues/`; recommends changes but does not apply them.Votes: 0GitHub stars: 13
- Code RefactorProduces a target design and an incremental migration sequence for a codebase, backed by an architectural review. Use when asked how a system should be refactored, restructured, or reorganized, or what it should look like afterward. Writes its findings and plan to `.issues/`; recommends changes but does not apply them.Votes: 0GitHub stars: 13
- Code TheoryBuilds a Naur-style theory of a codebase — the understanding needed to change it without damaging its conceptual integrity. Use when inheriting an unfamiliar system, capturing design rationale, or recovering lost design intent. Writes `THEORY.md` plus any drift and contradictions it finds to `.issues/`.Votes: 0GitHub stars: 13
- Code WalkthroughReads source code and produces a linear walkthrough document. Use when explaining how code works, creating walkthroughs, onboarding to a project, or giving a code tour. Writes `WALKTHROUGH.md`, plus any stale or inexplicable code it hits to `.issues/`.Votes: 0GitHub stars: 13
- Release GateValidates a repository is ready to tag and ship. Use when tagging or cutting a release/version, running a pre-release check, or asking "are we ready to release?" Checks repo hygiene, CI status, docs, version sync, and build verification.Votes: 0GitHub stars: 13
- Release ShipExecutes the release workflow for a repository after release-gate passes. Use when tagging, cutting, or shipping a release. Follows the prep-PR pattern: version bump, CHANGELOG, and walkthrough ship in one PR before tagging.Votes: 0GitHub stars: 13
- Issue PrFixes one issue and lands it as a merged pull request — branch, implement, run the repo's own gate, open a PR that closes the issue, wait for CI, merge. Use when asked to fix, do, or ship a specific issue.Votes: 0GitHub stars: 13
- Issue TriageOrganizes filed issues into milestones and repairs their metadata — severity labels, blocked-by relations, and project-board fields. Use when sorting a backlog, planning a release's scope, recording what blocks what, or when issues have been filed but not placed.Votes: 0GitHub stars: 13
- Issue VerifyRe-reads open issues against the current tree and posts a verification comment on each, flagging anything already fixed, partly stale, or wrong to do. Use before acting on a backlog, triaging a milestone, or when asked whether filed issues are still real.Votes: 0GitHub stars: 13
- Release CaptainWorks an entire milestone unattended: verifies every open issue, sequences them by dependency, ships each as a merged PR, then stops when the milestone is empty, before release prep. User-invoked only — it merges pull requests.Votes: 0GitHub stars: 13