All authors

Claude Skills by thermiteau
github.com/thermiteau41 skills0 installs83 views
- Do AdoptScan a project for missing best-practice areas and implement the top recommendation for each gap. Currently covers linting and unit testing. Installs tools, writes configs, and adds CI steps.Votes: 0GitHub stars: 11
- Do CodeImplement a focused code change. Use this skill as the wrapper for any implementation work so the Maverick workflow report captures what was done and so the agent applies the project's coding standards before editing. Intended to be invoked once per task from inside a do-issue-* or do-epic phase, not standalone.Votes: 0GitHub stars: 11
- Do Cybersecurity ReviewRun a security audit of the project's existing codebase and write a findings report to docs/security-audit.md. Covers secrets exposure, dependency vulnerabilities, authentication and authorisation patterns, input validation, transport security, and common OWASP risks. Run as part of do-init or on demand.Votes: 0GitHub stars: 11
- Do DocsCreate, restructure, or update technical documentation. Handles greenfield projects, refactoring non-compliant docs, and incremental updates after code changes.Votes: 0GitHub stars: 11
- Do EpicWork on a multi-story GitHub epic end-to-end. Builds a DAG from the child stories, groups them into waves, runs waves in parallel via per-story worktrees, ejects PRs that fail agent-code-review for human handling, and propagates blocks to downstream stories. Requires git worktrees.Votes: 0GitHub stars: 11
- Do InitInitialise a project for use with Maverick — verifies the GitHub App, installs the CLI if needed, writes the project config with integration tracking, scaffolds docs, generates project skills, runs an initial cybersecurity audit, then commits the changes and opens a PR.Votes: 0GitHub stars: 11
- Do InstallInstall the maverick CLI tool system-wide from the plugin directory.Votes: 0GitHub stars: 11
- Do Issue GuidedWork on a GitHub issue interactively with the user. Proceeds autonomously through routine work but pauses for confirmation at key decision points and when uncertain.Votes: 0GitHub stars: 11
- Do Issue SoloWork on a GitHub issue end-to-end autonomously, only pausing when blocked or when clarification is needed.Votes: 0GitHub stars: 11
- Do Maverick AlignmentAnalyze a project's codebase against Maverick standard practices and write a findings report. Checks linting, unit tests, integration tests, documentation, CI/CD, security, dependency management, observability, source control, and more. Run when onboarding an existing project or on demand.Votes: 0GitHub stars: 11
- Do Pullrequest ReviewHow to process code review feedback — verify before implementing, push back when wrong, clarify before acting on partial understanding. Applied when receiving review from the code-reviewer agent or human reviewers.Votes: 0GitHub stars: 11
- Do Tech DocsTechnical documentation standards — document structure, writing style, file organisation, mermaid diagrams, and validation. Referenced by do-docs and tech-docs-writer.Votes: 0GitHub stars: 11
- Do TestWrite or update tests for a code change. Operates in two modes: `unit` (module-scoped, fast, deterministic) and `integration` (crosses module / service / database boundaries). Intended to be invoked once per testable change from inside a do-issue-* or do-epic phase. Mode is required.Votes: 0GitHub stars: 11
- Do UpskillUse when a best-practice skill needs project-specific implementation details and no project skill exists at docs/maverick/skills/<topic>/SKILL.md. Scans the codebase and generates a project-specific skill file.Votes: 0GitHub stars: 11
- Mav Block PropagationIdempotent, resumable propagation of a `blocked-by:#N` block from an ejected story to every transitive downstream story in the epic DAG. Triggered when agent-code-reviewer ejects a PR for human handling.Votes: 0GitHub stars: 11
- Mav Bp AccessibilityAccessibility conventions for projects with user-facing interfaces. Covers WCAG 2.1 AA compliance, semantic HTML, keyboard navigation, colour contrast, screen reader support, and automated a11y testing. Applied when building or reviewing user-facing web or mobile applications.Votes: 0GitHub stars: 11
- Mav Bp Api DesignAPI design conventions for projects with API surfaces. Covers REST and GraphQL standards, versioning, error formats, pagination, documentation as code, and backwards compatibility. Applied when designing, implementing, or reviewing APIs.Votes: 0GitHub stars: 11
- Mav Bp Application SecurityApplication security conventions for all projects. Covers OWASP Top 10 awareness, input validation, secrets management, dependency scanning, SAST/DAST integration, and security headers. Applied when writing or reviewing any code.Votes: 0GitHub stars: 11
- Mav Bp CicdPlatform-agnostic CI/CD conventions. Covers pipeline stages, quality gates, environment promotion, secrets management, artifact handling, and deployment boundaries. Applied when configuring or reviewing CI/CD pipelines.Votes: 0GitHub stars: 11
- Mav Bp Code ReviewCode review conventions for all projects. Covers mandatory review requirements, review scope, PR sizing, reviewer and author responsibilities, and automated review integration. Applied when creating or reviewing pull requests.Votes: 0GitHub stars: 11
- Mav Bp Database ManagementDatabase and data management conventions for all projects using databases. Covers schema migrations, backup strategy, data lifecycle, index management, and connection pooling. Applied when designing, implementing, or reviewing database interactions.Votes: 0GitHub stars: 11
- Mav Bp Dependency ManagementDependency management conventions for all projects. Covers lock files, version pinning, vulnerability scanning, license compliance, update strategy, and minimal dependency principle. Applied when adding, updating, or reviewing dependencies.Votes: 0GitHub stars: 11
- Mav Bp Environment ManagementEnvironment management conventions for all projects. Covers reproducible local development, environment parity, .env patterns, developer onboarding, and containerised development. Applied when setting up or reviewing development environments.Votes: 0GitHub stars: 11
- Mav Bp Error HandlingError handling conventions for all applications. Covers error propagation, retry strategies, circuit breakers, graceful degradation, error boundaries, and typed errors. Applied when writing or reviewing error handling code.Votes: 0GitHub stars: 11
- Mav Bp Infrastructure As CodeInfrastructure as Code conventions for all deployed projects. Covers IaC principles, environment parity, secrets management in IaC, version control, and runbook fallback for unsupported platforms. Applied when reviewing or configuring infrastructure.Votes: 0GitHub stars: 11
- Mav Bp LintingLinting conventions for applications. Covers linter selection, rule configuration, auto-formatting, CI integration, and project linting guidance. Applied when writing or reviewing code, or configuring developer tooling.Votes: 0GitHub stars: 11
- Mav Bp Remote Code ReviewMandatory remote code review on every pull request. Defines the contract for a GitHub Actions workflow that runs the agent-code-reviewer in CI when a PR is opened, synchronized, or reopened. Used as a dependency by do-issue-solo and do-epic to enforce the review gate, and by do-maverick-alignment to audit the workflow's presence.Votes: 0GitHub stars: 11
- Mav Claude Code RecoveryPatterns for Claude Code workflow resilience — state persistence, crash recovery, command failure handling, subagent failure handling, and artefact durability. Not about application-level error handling.Votes: 0GitHub stars: 11
- Mav Create Solution DesignHow to produce a solution design for a GitHub issue or task. Covers codebase exploration, design structure, and validation. Used as a dependency from workflow skills.Votes: 0GitHub stars: 11
- Mav Create TasksHow to decompose a solution design into discrete, independently implementable tasks. Used as a dependency from workflow skills.Votes: 0GitHub stars: 11
- Mav Durability On GhDurability conventions for multi-instance Maverick workflows. Covers cold-start hydration from GitHub, marker-write protocols, push-per-task cadence, and recreating worktrees from remote branches. GitHub is the source of truth; local files are a cache.Votes: 0GitHub stars: 11
- Mav Git WorkflowGit branching strategy, commit conventions, merge conflict handling, and branch lifecycle. Implements a simplified Gitflow with protected branches and conventional commits. Covers worktree-based multi-story workflows and cross-references stacked-PR handling.Votes: 0GitHub stars: 11
- Mav Github Issue WorkflowStandard patterns for interacting with GitHub issues — reading, commenting, updating, state tracking, branching, and PR creation. Use as a dependency from workflow skills, not directly.Votes: 0GitHub stars: 11
- Mav Local VerificationPre-push code quality verification — lint, typecheck, and tests run locally before pushing. Covers discovering project verification commands, run order, scope-appropriate checks, and fixing failures. Used as a dependency from workflow skills.Votes: 0GitHub stars: 11
- Mav Multi Instance CoordinationClaim, lease, heartbeat, and release protocols for when multiple Claude Code instances may act on the same issue or epic concurrently. GitHub labels and marker comments are the coordination surface; local state is a cache.Votes: 0GitHub stars: 11
- Mav Plan ExecutionHow to execute an implementation plan step-by-step. Covers the execution loop, verification discipline, failure handling, progress tracking, crash recovery, and acceptance criteria. Adapts behaviour based on whether the caller is solo (autonomous) or guided (human checkpoints). Used as a dependency from workflow skills.Votes: 0GitHub stars: 11
- Mav Scope BoundariesDefines what Claude Code must refuse to do without explicit authorisation. Covers infrastructure, auth, destructive git, and production systems. Applied automatically to all workflows.Votes: 0GitHub stars: 11
- Mav Stacked PrsHow to stack a PR on top of an unmerged sibling branch, and how to retarget it to the repo's default branch once the sibling merges. Prevents orphan-merge incidents when a dependent story is ready before its parent.Votes: 0GitHub stars: 11
- Mav Systematic DebuggingUse when encountering any bug, test failure, or unexpected behaviour during implementation. Requires root cause investigation before proposing fixes.Votes: 0GitHub stars: 11
- Mav Bp OperabilityOperability standards — logging, alerting, and observability as one discipline. Maverick''s opinionated rules: error-only log levels (no info), structured JSON logs, alert-at-the-boundary, correlation across logs/metrics/traces. Applied when writing or reviewing code that logs, alerts, or instruments.Votes: 0GitHub stars: 11
- Mav Bp TestingTesting standards — unit and integration testing as one discipline. Maverick''s opinionated rules: behaviour over implementation, mock at boundaries only, 60% unit-coverage CI gate, critical-path integration coverage with a no-decrease ratchet. Applied when writing or reviewing tests.Votes: 0GitHub stars: 11