jcdendrite
@jcdendrite
Public Skills
tighten-prose
by jcdendrite
Rewrite prose for clarity and concision — short sentences, active voice, one idea per sentence, consistent terminology — without dropping or softening any fact, number, decision, or hedge. Operates on a drafted PR body, handoff note, or literal input text by default; rewrites durable in-repo content only when the invocation names it. Dispatched by /pr-description's prose-tightening pass; also invocable standalone any time drafted text needs the same treatment.
branch-management
by jcdendrite
Name a feature branch, start it clean, and anchor the session in its worktree. TRIGGER when: creating a new feature branch, picking a branch name, deciding whether to use a tracker-provided default branch name, entering or re-entering a branch's worktree, starting work in a resumed session. DO NOT TRIGGER when: routine work on an existing branch already anchored in its worktree, syncing a branch with the default (use git-feature-branch-sync instead), or force-pushing.
error-handling
by jcdendrite
Error-handling: envelope, propagation, and capture rules for server-side APIs. TRIGGER when: reviewing server-side catch blocks, response formatters, telemetry capture, or serverless error boundaries; defining or auditing application error codes or the code registry; reviewing API error response shapes. DO NOT TRIGGER when: reviewing client-side error display only with no server path in diff; reviewing test assertions on error shapes without touching production code.
root-cause-analysis
by jcdendrite
"A playbook for debugging and root-cause investigation: establish the full symptom, verify tool ingestion, reproduce and capture the asymmetry, pull data for the specifically affected entities, then confirm the fix addresses the reported incident before shipping."
test-conventions
by jcdendrite
Testing conventions for writing tests in any codebase. TRIGGER when: planning tests for new code, writing test infrastructure (mocks, helpers, fixtures), or discussing test strategy for new features. DO NOT TRIGGER when: the task is purely mechanical (running tests, fixing a single assertion, updating a snapshot), or evaluating/debugging an existing test suite (use test-evaluation).
respond-pr
by jcdendrite
"Respond to PR review comments on the current branch's PR. Enforces required attribution prefix. The gate matches command shape, so it fires on any branch and with no unread comments. TRIGGER when: reading or posting any PR/issue comment or review in this repo. DO NOT TRIGGER when: no comment read or post is attempted, or it only reads another repo."
read-docx-comments
by jcdendrite
Extract all comments from a .docx file (Google Docs / Word feedback) and present them grouped by document location with author and anchored text.
test-evaluation
by jcdendrite
Evaluate and debug existing test suites. TRIGGER when: reviewing or evaluating an existing test suite, debugging slow or flaky tests, assessing test coverage quality, or reviewing test code. DO NOT TRIGGER when: writing new tests (use test-conventions), or the task is purely mechanical (running tests, fixing a single assertion, updating a snapshot).
agent-review
by jcdendrite
Audit of agent files: frontmatter, triggers, voice, length, duplication. TRIGGER when: authoring/reviewing a .claude/agents/.md or plugins//agents/*.md change, or auditing trigger accuracy across the roster. DO NOT TRIGGER when: editing SKILL.md (use skill-review), editing CLAUDE.md/AGENTS.md/memory files (use ai-instruction-and-memory-files), or reviewing non-agent files.
verify-sources
by jcdendrite
Confirm claims at the primary source — fetch the official docs, spec, or source directly. TRIGGER when: researching a library, API, framework, or architecture/design decision; or acting on a documentation claim from a subagent, blog post, or other secondary source. DO NOT TRIGGER when: you want a multi-source research synthesis (that is a research-harness job, not source verification); quick syntax lookups; error decoding; or when the cited URL is already the primary source.
error-mode-analysis
by jcdendrite
Produce a signal-bucketed error-mode report from a delivered body of multi-session AI-assisted work — bucket every failure by which pipeline layer caught it, correlate transcript signals with PR review comments, and split output into a private, project-identifying report and a de-identified public lessons doc. Builds on transcript-narrative and transcript-analysis. Supports a multi-window trend pass to distinguish recurring patterns from one-off noise.
lovable-cloud-knowledge
by jcdendrite
Lovable's UI knowledge fields and workspace skill files — .lovable/.md repo-mirror workflow, .agents/skills/ propagation model, Project/Workspace scope split, precedence, review criteria. TRIGGER when: authoring or reviewing changes to .lovable/.md or .agents/skills/*.md; drafting Project/Workspace Knowledge or workspace-skill changes. DO NOT TRIGGER when: not a Lovable project; editing CLAUDE.md or AGENTS.md; editing agent rules files; writing code.
issue-triage
by jcdendrite
Evidence-backed, report-only GitHub issue triage. Invoke directly with /issue-triage — not auto-triggered by the model.
linear-formatting
by jcdendrite
Linear issue-comment and issue-link formatting conventions for tracker writes: issue-ID auto-linking, comment markdown support, the create/update tool-shape variance across Linear MCP server versions, the required Claude-authorship attribution prefix, real-newline formatting, and the repeated-issue-reference auto-linker drop. TRIGGER when: posting or editing a Linear issue comment or document, or writing text that references a Linear issue ID for a Linear-tracked repo. DO NOT TRIGGER when: the tracker is not Linear (e.g. Jira, GitHub Issues), or the write touches only a status/assignee field with no comment or document body.
plan-review-claude-config
by jcdendrite
Project-specific layer for /plan-review, loaded only when reviewing plans in the claude-config repo itself.
lovable-cloud-migration-sync
by jcdendrite
Post-apply cleanup for Lovable-duplicated migrations: diff originals, db reset, delete, open PR. TRIGGER when: the user signals Lovable's migration apply step completed, regardless of exact wording. DO NOT TRIGGER when: all originals already deleted, or user asks about mechanics without signaling completion.
lovable-cloud-edge-functions
by jcdendrite
Supabase edge function authentication, config.toml, and Lovable Cloud deployment. TRIGGER when: adding, modifying, or reviewing an edge function in a Lovable Cloud project, or modifying a file that configures one (e.g. supabase/config.toml) or invokes one (e.g. pg_cron). DO NOT TRIGGER when: no edge function configured, invoked, or modified.
npm-semver
by jcdendrite
Semver and version-field discipline for published npm packages, plus a reminder to propagate a bump into consuming repos. TRIGGER when: editing the source of a published npm package, or preparing to publish one. DO NOT TRIGGER when: the package.json has "private": true, or the repo only consumes the dependency rather than publishing it.
plugin-semver
by jcdendrite
Semver and version-field discipline for Claude Code plugin changes. TRIGGER when: modifying any file inside a plugin directory (tree contains .claude-plugin/plugin.json), or editing a .claude-plugin/marketplace.json. DO NOT TRIGGER when: editing skills/agents outside any plugin — e.g. user-scope stowed skills.