donnfelker-plugin-marketplace

This skill should be used when the user asks to "generate release notes", "generate changelog", "create release notes", "write changelog", "what changed since last release", "prepare release notes", "update changelog", or "summarize changes from git history". Parses conventional commit messages to produce categorized, well-formatted release notes or changelog entries.

Scouts an agent conversation for skill opportunities and produces a markdown report of recommended new skills and edits to existing ones, then hands off to /skill-creator or edits the affected SKILL.md directly. Use this skill when the user says "skill scout", "scout this conversation", "scout for skills", "audit this conversation for skills", "what skills would have helped here", "extract skills from this chat", or "any skill gaps from this session". Also use it to mine a PAST session — "recommend skills from a previous conversation", "scout my last session", "what skills would have helped in that earlier session" — in which case it scans saved transcripts under ~/.claude/projects/. Looks for five signals: manual workflows worth packaging, skill output that had to be corrected, repeated user corrections, reusable multi-step research, and skill content to simplify or remove. To draft skills see /skill-creator; to verify quality see /plugin-dev:skill-reviewer.

Searches past Claude Code session transcripts under ~/.claude/projects/ to recover a previous conversation by recalled phrase, error string, or topic. Use when the user says 'search your history for', 'find the conversation about', 'look through your past sessions', 'did I ever finish that work on', 'what did we decide about X last week', 'remind me what came out of that session', or otherwise asks you to recall a prior session. Returns session ID, project, date, and a 2-4 sentence summary; on request, also reports the outcome (commit, branch, PR opened or merged). Not for searching the current codebase, current PR comments, or external systems like Slack/Jira — for those, see codebase-analyzer and address-pr-comments.

When the user wants a comprehensive technical analysis of a codebase or project. Also use when the user mentions 'analyze this codebase,' 'technical overview,' 'document this architecture,' 'what does this codebase do,' 'summarize this repo,' 'code audit,' 'architecture review,' 'codebase walkthrough,' or 'analyze this project.' Performs a multi-phase analysis covering architecture, code quality, testing, and infrastructure, producing a detailed markdown report targeting engineers. For quick code searches or single-file reviews, see standard editor tools.