This skill should be used when the user requests a code review, audit, or quality assessment covering quality, security, dependencies, and documentation. It uses parallel agents and produces a deduplicated, severity-ranked report.
This skill should be used when extracting learnings, saving lessons, or capturing reusable knowledge from a session. It is also appropriate before presenting a plan, after notable events such as bugs or corrected approaches, and as the final task when work is complete.
This skill should be used when the user asks to "merge the base branch", "update this feature branch from base", or resolve conflicts while merging base into a feature branch.
This skill should be used when the user asks to "commit and push", "create a PR", "ship this", "send changes upstream", "open a pull request", or "publish this branch". It commits, pushes, creates a PR, and automatically creates a feature branch when currently on a base branch.
This skill should be used when the user asks to "bump the version", "cut a release", or "create a GitHub release". It applies SemVer 2.0, updates the changelog, commits, pushes, creates the release, and auto-detects Rust, Python, JS/TS, Claude Code plugin, and other supported stacks. Arguments are major, minor, patch…
This skill should be used when the user asks to "review a dependency update", "audit this dependency bump", or assess the security of an upgraded or newly added dependency.
This skill should be used when the user asks to "review this PR", "audit this pull request", or assess a PR for code quality, security, and correctness.
This skill should be used when implementing, fixing, writing, reviewing, or discussing Rust code quality, API design, safety, or idioms. It applies the Microsoft Pragmatic Rust Guidelines and Rust API Guidelines checklists.
This skill should be used when writing or reviewing code that handles authentication, cryptography, user input, secrets, or API endpoints. It provides OWASP-based secure programming practices and should be consulted proactively during reviews and planning.
This skill should be used when tracking delegated or multi-step work in a durable store that survives context loss — before spawning agents, while a multi-task wave is in flight, and after compaction or other context loss to recover pending work. It applies to solo, delegated, and multi-agent work alike.
This skill should be used when the user explicitly asks to "triage findings" through an interactive browser-based workflow. Only invoke when explicitly requested.
This skill should be used when the user says "triage" or asks to triage a GitHub issue: reproduce it, identify the root cause and owning component, estimate severity, discuss the findings with the user, and then post a short status comment.
This skill should be used when a coordinator performs the LLM validation pass on a consolidated v4 findings report. It adds aiassessment, aiverdict, and aiverdictconfidence and, in the rare partial-producer case, re-estimates missing likelihood, impact, and relevance. Coordinator-only.
This skill should be used when the user asks to "build a new project", "add a feature", or perform a major refactoring. It runs Planning (Req→UX→Test Spec→Dev Plan) → Implementation → QA → Lessons Learned, with unattended auto-retry on failure.
This skill should be used when handling a bug fix or small-to-medium change of no more than 1000 LOC. One high-capability agent runs plan → TDD tests → implementation → self-review/self-fix end-to-end from a WHAT-not-HOW brief, unattended.