popoffvg

Use when drawing a diagram of an architecture change for review — a two-panel current-vs-planned (before/after) picture that lets a reviewer see what changed, what's removed, what's new, what held, and the one load-bearing why. Triggers: "arch diagram", "architecture diff", "before/after diagram", "diagram this refactor/migration/change", "visualize the change", "current vs planned", or any request to render an architectural change as a reviewable picture (HTML/SVG).

Use when asked to create a "local gitignore" or ignore files locally without committing the ignore rule. Create a `.gitignore.local` file at repo root and wire it via `git config core.excludesFile`, not `.git/info/exclude`.

This skill should be used when the user asks to "dedup the docs", "prune the corpus", "remove duplicate/redundant paragraphs", "reduce duplication across files", "these files repeat the same information", "consolidate repeated content", "the corpus duplicates topics", "map topics across files", or wants to find and remove duplicated prose across a set of text files (plain prose, markdown, SKILL.md, references, commands, specs).

This skill should be used when the user runs "/prx", "/prx <pr-url>", or "/prx post" — to collect the user's review comments against a diff and post them as an inline GitHub PR review. Trigger on "collect my PR comments", "start collecting comments", "post my comments to the PR", "send the review comments".

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Manage spec writing, implementation, and bug fixing.

This skill should be used when asked about branching, committing, PRs, or the end-to-end Git development flow. Covers available commands (/smart-commit, /pr, /code fix), branch naming conventions, and when to use each tool.

Use it when user ask describe the flow or write pseudocode.

This skill should be used when the user says "work done", "done with work", "finish work", "mark complete", "close work". Mark work complete by updating the work note.

This skill should be used when the current work phase is "implement". Provides the implementation workflow: reading the plan, executing tasks, running tests, saving results to _notes/impl-*.md, handling blockers, and checking completion criteria.

This skill should be used when the user says "work install", "install work manager", "setup work manager", "configure work manager", "work setup", "set up mise tasks", "install mise tasks". Guides through full work-manager setup: plugin installation, mise tasks, QMD, and environment configuration.

This skill should be used when the current work phase is "plan". Provides the planning workflow: reading research notes, building acceptance criteria, creating ordered task lists with parallelization strategy, saving design decisions to _notes/plan-*.md, and transition to implement phase.

This skill should be used when the user says "work pr", "create PRs", "open pull requests for my repos". Create PRs for all repos in the current workspace that have unpushed commits.

This skill should be used when the user says "work recall", "where was I", "what was I working on", "resume work". Re-orient to current work — read notes, synthesize status, suggest next step.

This skill should be used when the current work phase is "research". Provides the research workflow: scope breakdown, codebase exploration, saving findings to _notes/research-*.md, and transition to plan phase.

This skill should be used when the user says "start work", "work start", "begin work", "initialize work". Start new work — detect branch, gather details, plan, save work note with hierarchical work notes structure.

This skill should be used when the user says "context check", "check for insights", "anything worth saving", "review session", or wants to analyze the current conversation for valuable learnings worth persisting — debugging discoveries, architectural decisions, corrections, workflow patterns.

This skill should be used when the user says "context save", "remember this", "save this", "note this for later", "keep this", or wants to persist any knowledge, pattern, decision, or learning from the current session to persistent memory.

Scan recent Claude session logs for missed insights (fallback when Stop hook fails). This skill should be used when the user says "context scan", "scan sessions", "check old sessions", "find missed insights", or wants to recover insights from sessions where the Stop hook did not fire. Also used by hourly cron to automatically sweep for uncaptured knowledge.

This skill should be used when the user says "work done", "context done", "task done", "finish task", "complete task", "close task", or indicates they have finished working on an active task. Summarizes task insights and distributes them to each repo's insight folder.

Search and retrieve insights from persistent memory. This skill should be used when the user says "context find", "recall", "what do I know about", "find my notes on", "search memory", "do I have anything on", or wants to retrieve previously saved knowledge. Always invoke to check memory before answering any topic-based question.

This skill should be used when the user says "research", "look into", "look up", "find out about", "search for", or asks about a topic needing investigation. Checks persistent memory first, performs web research if insufficient, persists results.