claudius

Use for system design, module boundaries, dependency review, architectural trade-offs, technology evaluation, library comparison, or validating plans before presenting to user.

Personal software development assistant. Leads and coordinates development efforts. Always invoked when user interaction is needed.

Bilby. Use for code changes or language-specific code quality reviews in any language (Rust, Python, Go, TypeScript/JS, frontend).

Use for reviewing PRs or auditing project consistency across code, configs, docs, and tests. Read-only — NOT for language-specific code quality.

Use to validate that code matches requirements. Audits test coverage against specs, executes tests, and reports all mismatches.

Use for security audits, auth/crypto/input validation reviews, dependency scanning, secret detection, or validating plans before presenting to user.

Use for creating, maintaining, or reviewing documentation — READMEs, API docs, tutorials, guides, changelogs, ADRs.

Use at project start for requirements, domain analysis, stakeholder mapping, or during design for UI flows, interaction patterns, usability, accessibility, and validating plans before presenting to user.

Use to verify PR review comments are addressed in code. Optionally produces triage-compatible report.

This skill should be used when the user says 'ci-dance', 'make the PR green', 'ship this and fix CI', 'push and handle reviews', or wants end-to-end PR pipeline automation.

Use to autonomously fix CI failures — watch runs, diagnose, fix, push, repeat until green.

Use when developing code. Universal rules for TDD, self-review, quality timing, review format, security. Preloaded on developers.

Bulk-process open dependabot PRs: audit each dependency, comment findings, merge if CI green, request rebase on conflicts or CI failures. Use to merge dependabot PRs, process dependency bumps, auto-merge bot PRs, or handle dependabot backlog.

Frontend best practices — TypeScript, React/Vue/Svelte, CSS, accessibility, testing. Use when writing, reviewing, or discussing frontend code.

Invoke for all git and gh commands, GitHub interactions. Solves git and gh access / permission denied issues.

Go best practices — idioms, error handling, concurrency, testing patterns. Use when writing, reviewing, or discussing Go code.

Parallel-agent code review for quality, security, dependencies, and docs. Use for reviews, audits, or quality assessments. Produces deduplicated severity-ranked report.

Use when extracting learnings, saving lessons, or capturing reusable knowledge from the session. Also appropriate before presenting a plan, after notable events (bugs, wrong approaches corrected), and as final task when work is complete.

Use for merging base into feature branch with conflict resolution.

Commit, push, and create PR. Auto-creates feature branch if on base. Use when user wants to commit and push, create a PR, ship work, send changes upstream, open a pull request, or publish a branch.

Python best practices — PEP 8, type hints, testing, error handling, code quality tools. Use when writing, reviewing, or discussing Python code.

Bump version (SemVer 2.0), update changelog, commit, push, and create GitHub release. Auto-detects project tech stack (Rust, Python, JS/TS, Claude Code plugins, etc.). Args: major|minor|patch or auto-detect from commits. User-invocable only — agents must not invoke this skill autonomously.

Unified review report format for all finding-producing agents. Load when emitting or consuming review findings.

Use for security review of dependency updates — bumps, upgrades, or new dependencies.

Use to autonomously handle peer review — request, wait, fix comments, push, repeat until resolved.

Use to review a PR for code quality, security, and correctness.

Rust best practices checklists (Microsoft Pragmatic + Rust API Guidelines). Use when writing, reviewing, or discussing Rust code quality, API design, safety, or idioms.

OWASP-based secure programming practices. Use when writing or reviewing code handling auth, crypto, user input, secrets, or API endpoints. Consult proactively during reviews and planning.

Use when rating findings in reviews, audits, and assessments. Preloaded on finding-producing agents.

Use for interactive browser-based triage of review findings. Only invoke when explicitly requested.

Use for new projects, features, or major refactoring. Phases: Requirements → Architecture → TDD → Implementation → QA → Lessons Learned.

Use for bug fixes or small changes (≤200 lines). Phases: Requirements → Architecture → TDD → Implementation → QA → Lessons Learned (lighter ceremony).

Use for typos or single-line fixes (≤20 lines). Phases: TDD → Implementation → QA → Lessons Learned.

2 hooks across 2 events