philoserf
- 25 skills
- 0 followers
- 13 repo stars
- last month last updated
- ▌ Editor 2 · philoserf bundleCopy 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.
- ▌ Taskfile · philoserfRuns and authors Taskfiles with the go-task `task` runner (Taskfile.yml, version 3). Use when running a task, listing/discovering tasks, passing variables or CLI args, or writing/editing task definitions, deps, up-to-date checks, or includes.
- ▌ Code Audit 2 · philoserfReviews 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/`.
- ▌ Deps Audit · philoserfAudits project dependencies for vulnerabilities, outdated packages, and license issues. Use when checking dependency health, running security audits, or reviewing package versions. Covers native audit tools, version freshness, and license compliance.
- ▌ Walkthrough · philoserfReads 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. Generates structured showboat documents with annotated code paths.
- ▌ Obsidian CLI · philoserf bundleInteracts with Obsidian vaults via the Obsidian CLI. Use when working with a vault, adding to daily notes, querying by tag/link, automating vault tasks, or debugging plugins/themes. Manages notes, frontmatter properties, tags, bookmarks, templates.
- ▌ Skill Cleaner · philoserf bundleAudits ~/.claude/skills/ for hygiene issues. Use when trimming the skill set, asking which skills are unused or most-used, or finding duplicates. Reports usage frequency, unused skills, duplicates, and missing or overlong descriptions.
- ▌ Code Reduction 2 · philoserfReviews 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. Advisory only.
- ▌ Codebase Theory · philoserfBuilds 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`.
- ▌ Obsidian Release Gate · philoserf bundleValidates 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.
- ▌ Obsidian Release Ship · philoserf bundleExecutes the release workflow for Obsidian plugins after obsidian-release-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.
- ▌ Frames 2 · philoserf bundleGenerates 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.
- ▌ Cc Release Review 2 · philoserf bundleReviews 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.
- ▌ MCP Toggle Normalize 2 · philoserfRe-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.
- ▌ Code Audit · philoserf bundleReviews 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/`.
- ▌ Code Theory · philoserfBuilds 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/`.
- ▌ Code Refactor · philoserf bundleProduces 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.
- ▌ Obsidian Gate · philoserf bundleValidates 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.
- ▌ Obsidian Ship · philoserf bundleExecutes 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.
- ▌ Code Reduction · philoserfReviews 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.
- ▌ Code Walkthrough · philoserfReads 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/`.
- ▌ Cc Release Review · philoserf bundleReviews 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.
- ▌ Editor · philoserf bundleCopy 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.
- ▌ Frames · philoserf bundleGenerates 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.
- ▌ MCP Toggle Normalize · philoserfRe-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.