Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

philoserf

@philoserf source repo

11 published skills

  1. ▌
    Code Audit · philoserf bundle
    Reviews 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/`.
    0
    installs
  2. ▌
    Code Theory · philoserf
    Builds 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/`.
    0
    installs
  3. ▌
    Code Refactor · philoserf bundle
    Produces 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.
    0
    installs
  4. ▌
    Obsidian Gate · philoserf bundle
    Validates an Obsidian plugin 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.
    0
    installs
  5. ▌
    Obsidian Ship · philoserf bundle
    Executes the release workflow for Obsidian plugins after obsidian-gate passes. Use when tagging, cutting, or shipping a plugin release. Follows the prep-PR pattern: version bump, CHANGELOG, and walkthrough ship in one PR before tagging.
    0
    installs
  6. ▌
    Code Reduction · philoserf
    Reviews 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.
    0
    installs
  7. ▌
    Code Walkthrough · philoserf
    Reads source code and produces a linear, executable walkthrough document. Use when explaining how code works, creating walkthroughs, onboarding to a project, or giving a code tour. Writes `WALKTHROUGH.md` via showboat, plus any stale or inexplicable code it hits to `.issues/`.
    0
    installs
  8. ▌
    Cc Release Review · philoserf bundle
    Reviews 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.
    0
    installs
  9. ▌
    Editor · philoserf bundle
    Copy 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.
    0
    installs
  10. ▌
    Frames · philoserf bundle
    Generates options for an open-ended decision by fanning out isolated subagents under different cognitive frames, then synthesizing. Use for design decisions, API and naming choices, architecture questions, fuzzy debugging, strategy, and any request shaped like "give me a few ways to…". Advisory only — produces options, not edits.
    0
    installs
  11. ▌
    MCP Toggle Normalize · philoserf
    Re-normalizes MCP connector enable/disable state across all project entries in ~/.claude.json (computer-use on; claude-in-chrome and claude.ai connectors off). Use when project dirs drift off the connector spec and every entry needs fixing at once.
    0
    installs