lorcan-claude-marketplace

Write a conventional-commits title and PR description for the current branch. Reads the raw diff vs base, asks heavily about why the change was made, then writes a humanised body in dropped-subject active voice with a Mermaid diagram where it helps. Never pushes, commits, or opens a PR.

Rewrite text and code to remove signs of AI-generated writing. Prose skill handles inflated significance, promotional language, em-dash overuse, AI vocabulary, bolded-header bullets, and sycophantic openers. Code skill renames verbose identifiers, simplifies comments and docstrings, and cleans up log / error / user-facing strings for non-native English readers.

Use when responding to code review or other critical feedback (PR comments, design review, written critique). Enforces verify-before-implement, reasoned push-back, one-item-at-a-time execution, and no performative agreement. Includes read-only gh helpers for PR context.

Write technical docs (architecture overviews, feature designs, runbooks, getting-started guides, READMEs, tech-debt notes, how-tos, implementation plans, RFCs, and more). Asks the doc type and audience first, runs targeted clarifying questions one at a time, then drafts in plain language with structured markdown and pastel mermaid diagrams where they help. Output is humanised, with no AI tells.