maverick-harness 5.0.0__tar.gz

maverick_harness-5.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

maverick_harness-5.0.0/PKG-INFO

@@ -0,0 +1,197 @@
+Metadata-Version: 2.4
+Name: maverick-harness
+Version: 5.0.0
+Summary: Claude Code plugin that enables autonomous AI development while maintaining best practices
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: boto3
+Requires-Dist: jinja2>=3.1
+Requires-Dist: pyjwt[crypto]>=2.8
+Requires-Dist: pyright>=1.1.408
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: ruff>=0.8
+Provides-Extra: test
+Requires-Dist: pytest>=8.0; extra == "test"
+Dynamic: license-file
+
+<!-- PROJECT LOGO -->
+<br />
+<div align="center">
+  <a href="https://github.com/thermiteau/maverick">
+    <img src="docs/media/maverick-logo.png" alt="Maverick Logo" width="200" height="200">
+  </a>
+
+  <h1 align="center">Maverick</h1>
+
+  <p align="center">
+    Claude Code tooling to build software right
+    <br />
+    <a href="docs/overview.md"><strong>Explore the docs</strong></a>
+    <br />
+    <br />
+    &middot;
+    <a href="https://github.com/thermiteau/maverick/issues/new?labels=bug&template=bug-report.md">Report Bug</a>
+    &middot;
+    <a href="https://github.com/thermiteau/maverick/issues/new?labels=enhancement&template=feature-request.md">Request Feature</a>
+  </p>
+</div>
+
+Maverick is a Claude Code ( Cursor and Codex ) plugin and local CLI commands that enables autonomous AI-driven software development while enforcing quality, security, and operational best practices.
+
+It provides skills, agents, and hooks that constrain and guide LLM behaviour - making unattended development safe and reliable.
+
+## The Problem Maverick Solves
+
+LLMs generate code fast but don't come with any concept of quality, best practice or constraint. Claude Code will happily agree to build the world's worst idea, with a smile, because without guardrails:
+
+- **No operational awareness** - LLMs don't add structured logging, alerting, or monitoring unless explicitly told to. Production code becomes undiagnosable.
+- **No security reasoning** - LLMs reproduce vulnerable patterns from training data. SQL injection, XSS, and secrets exposure go unnoticed. It won't make any effort to ensure cybersecurity is maintained.
+- **No testing discipline** - LLMs write working code and you can think you've got a product. Until it runs anywhere except on your machine, because it's filled with bugs you can't see. Without tests, those bugs ship.
+- **No workflow discipline** - LLMs commit to main, skip CI, ignore conventions, and produce untraceable changes. If you ask an LLM to create a large amount of changes in a single attempt it will try, and you'll regret it.
+- **No self-review** - LLMs don't question their own output. Code that looks correct may miss requirements or violate project conventions.
+
+These risks multiply enormously in unattended development when no human is watching the LLM work. There is no developer catching issues in real-time, no reviewer glancing at the diff, no operator noticing silent failures. Every quality gap becomes a production risk.
+
+## How Maverick Solves It
+
+Maverick is comprised of four parts:
+
+### Claude Code Plugin: Best practice
+
+Maverick comes with Claude Code skills that defines how to write quality code. These are not detailed technical skills, they are the why and how of software development practices. These skills are part of the plugin and get loaded into Claude Code.
+
+There are also a few technical skills that are so common, they have been predefined in the plugin.
+
+### Claude Code Plugin: Mechanical enforcement
+
+Safety rules are not prose the model can forget — the plugin ships hooks
+that enforce them at the tool-call boundary:
+
+- A **scope-guard hook** gates destructive git operations, commits and
+  pushes on protected branches, infrastructure edits, and
+  production-pattern commands. In interactive sessions rule hits ask you;
+  in autonomous runs they are denied outright. Production patterns are
+  denied in every mode.
+- Infrastructure changes in autonomous runs require **verified
+  issue-level authorization** (`maverick coord authorize`) — an agent
+  cannot self-grant a scope the issue never approved.
+- A **pre-merge auth scan** blocks auto-merging any PR that touches
+  authentication surfaces or CI workflow definitions, regardless of the
+  review verdict.
+- A **SessionEnd hook** releases coordination claims on every exit path,
+  and lease expiry covers machine death.
+
+### Claude Code Plugin: Skills creation
+
+Because every codebase is unique, there is no way to ship defined skills that are needed to enable Claude Code. So Maverick builds them when it is initialised in a project.
+
+- First it looks to see if you have them already, and uses yours if they are there.
+- If it cant find any, it reads your codebase and builds technical skills that match your tech stack and align with its best practice skills
+- These become part of your code and you can change them as required
+
+### Infrastructure as Code solution for remote Claude Code instances
+
+There are multiple ways to run Claude Code, the most obvious being the software running locally on your machine.  This works well for interactive development where you ask Claude Code to complete a task, answer any questions as they come up and monitor the progress.
+
+It falls down when you need to complete multiple features or bug fixes at the same time. Claude Code on local machines, doesnt scale.
+
+Maverick solves this by deploying Claude Code workers to remote Claude platforms such as Amazon Web Services. Those workers are triggered by creating tickets (issues) in GitHub. The worker will autonomously complete the requirements and keep you up to date with notes in the Github Issue.
+
+For most teams there is a simpler on-ramp first: a ready-made GitHub
+Actions workflow (`templates/github/claude-maverick.yml`) runs Maverick
+on GitHub-hosted runners — respond to `@claude` mentions, or label an
+issue `claude-do` and `do-issue-solo` works it end-to-end. See the
+remote-execution decision matrix in
+[docs/claude-code-workers.md](docs/claude-code-workers.md) for choosing
+between the GitHub Action, Claude cloud routines, and the self-hosted
+EC2 pipeline. None of this is required — the plugin works on your local
+machine and you can ask Claude to complete tasks solo or with
+assistance.
+
+## NOTE: This project is still in Alpha and under rapid change
+
+I use this repo to build my own software and I aim to improve it every day. That means the change rate is pretty high until I get it to v1 release.
+
+- The plugin skills, agents, and hooks are solid, and the full
+  `do-issue-solo` pipeline is exercised end-to-end against real
+  repositories.
+- The `maverick` CLI carries the workflow's deterministic core
+  (coordination, state, gates, reporting) with an extensive unit-test
+  suite; the AWS worker pipeline is in maintenance mode in favour of the
+  GitHub Action on-ramp for most use cases.
+
+## Install
+
+### Plugin
+
+```sh
+# Install the plugin (registers in ~/.claude/settings.json)
+claude plugin marketplace add https://github.com/thermiteau/maverick
+claude plugin install maverick@thermite
+```
+
+### CLI
+
+This makes the `maverick` command available globally.
+
+#### Prerequisites
+
+- Python 3.10+
+- [uv](https://docs.astral.sh/uv/) — Python package manager
+- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) — Anthropic's CLI for Claude
+- Claude Code API Key
+
+```sh
+# Install system-wide from the repo
+uv tool install .
+
+# Or install in development mode
+uv tool install -e .
+```
+
+## Usage
+
+### Initialising an existing project (repo)
+
+run `/maverick:do-init` within Claude Code
+
+### Work on GitHub issues
+
+With the plugin loaded, use skills directly in Claude Code:
+
+```sh
+/maverick:do-issue-solo 42
+# Autonomous mode — Claude works end-to-end, only pausing when blocked
+
+/maverick:do-issue-guided 42
+# Guided mode — Claude pauses for approval at design and plan phases
+
+/maverick:do-maverick-alignment
+# Audit a codebase against Maverick standards
+
+/maverick:do-adopt recommend
+# Recommend (or, without 'recommend', implement) missing best practices
+
+/maverick:do-upskill logging
+# Generate a project-specific implementation skill for one topic
+```
+
+Or skip the terminal entirely: copy
+`templates/github/claude-maverick.yml` into `.github/workflows/`, then
+label any issue `claude-do` and Maverick completes it on a GitHub-hosted
+runner — design, tasks, implementation, docs and security gates, PR,
+review, and merge.
+
+## Development
+
+```sh
+# Run unit tests
+uv sync --extra test && uv run pytest tests/unit/ -v
+```
+
+CI runs automatically on pushes and PRs to `main` via GitHub Actions.
+
+## License
+
+Apache License 2.0

maverick_harness-5.0.0/README.md

@@ -0,0 +1,180 @@
+<!-- PROJECT LOGO -->
+<br />
+<div align="center">
+  <a href="https://github.com/thermiteau/maverick">
+    <img src="docs/media/maverick-logo.png" alt="Maverick Logo" width="200" height="200">
+  </a>
+
+  <h1 align="center">Maverick</h1>
+
+  <p align="center">
+    Claude Code tooling to build software right
+    <br />
+    <a href="docs/overview.md"><strong>Explore the docs</strong></a>
+    <br />
+    <br />
+    &middot;
+    <a href="https://github.com/thermiteau/maverick/issues/new?labels=bug&template=bug-report.md">Report Bug</a>
+    &middot;
+    <a href="https://github.com/thermiteau/maverick/issues/new?labels=enhancement&template=feature-request.md">Request Feature</a>
+  </p>
+</div>
+
+Maverick is a Claude Code ( Cursor and Codex ) plugin and local CLI commands that enables autonomous AI-driven software development while enforcing quality, security, and operational best practices.
+
+It provides skills, agents, and hooks that constrain and guide LLM behaviour - making unattended development safe and reliable.
+
+## The Problem Maverick Solves
+
+LLMs generate code fast but don't come with any concept of quality, best practice or constraint. Claude Code will happily agree to build the world's worst idea, with a smile, because without guardrails:
+
+- **No operational awareness** - LLMs don't add structured logging, alerting, or monitoring unless explicitly told to. Production code becomes undiagnosable.
+- **No security reasoning** - LLMs reproduce vulnerable patterns from training data. SQL injection, XSS, and secrets exposure go unnoticed. It won't make any effort to ensure cybersecurity is maintained.
+- **No testing discipline** - LLMs write working code and you can think you've got a product. Until it runs anywhere except on your machine, because it's filled with bugs you can't see. Without tests, those bugs ship.
+- **No workflow discipline** - LLMs commit to main, skip CI, ignore conventions, and produce untraceable changes. If you ask an LLM to create a large amount of changes in a single attempt it will try, and you'll regret it.
+- **No self-review** - LLMs don't question their own output. Code that looks correct may miss requirements or violate project conventions.
+
+These risks multiply enormously in unattended development when no human is watching the LLM work. There is no developer catching issues in real-time, no reviewer glancing at the diff, no operator noticing silent failures. Every quality gap becomes a production risk.
+
+## How Maverick Solves It
+
+Maverick is comprised of four parts:
+
+### Claude Code Plugin: Best practice
+
+Maverick comes with Claude Code skills that defines how to write quality code. These are not detailed technical skills, they are the why and how of software development practices. These skills are part of the plugin and get loaded into Claude Code.
+
+There are also a few technical skills that are so common, they have been predefined in the plugin.
+
+### Claude Code Plugin: Mechanical enforcement
+
+Safety rules are not prose the model can forget — the plugin ships hooks
+that enforce them at the tool-call boundary:
+
+- A **scope-guard hook** gates destructive git operations, commits and
+  pushes on protected branches, infrastructure edits, and
+  production-pattern commands. In interactive sessions rule hits ask you;
+  in autonomous runs they are denied outright. Production patterns are
+  denied in every mode.
+- Infrastructure changes in autonomous runs require **verified
+  issue-level authorization** (`maverick coord authorize`) — an agent
+  cannot self-grant a scope the issue never approved.
+- A **pre-merge auth scan** blocks auto-merging any PR that touches
+  authentication surfaces or CI workflow definitions, regardless of the
+  review verdict.
+- A **SessionEnd hook** releases coordination claims on every exit path,
+  and lease expiry covers machine death.
+
+### Claude Code Plugin: Skills creation
+
+Because every codebase is unique, there is no way to ship defined skills that are needed to enable Claude Code. So Maverick builds them when it is initialised in a project.
+
+- First it looks to see if you have them already, and uses yours if they are there.
+- If it cant find any, it reads your codebase and builds technical skills that match your tech stack and align with its best practice skills
+- These become part of your code and you can change them as required
+
+### Infrastructure as Code solution for remote Claude Code instances
+
+There are multiple ways to run Claude Code, the most obvious being the software running locally on your machine.  This works well for interactive development where you ask Claude Code to complete a task, answer any questions as they come up and monitor the progress.
+
+It falls down when you need to complete multiple features or bug fixes at the same time. Claude Code on local machines, doesnt scale.
+
+Maverick solves this by deploying Claude Code workers to remote Claude platforms such as Amazon Web Services. Those workers are triggered by creating tickets (issues) in GitHub. The worker will autonomously complete the requirements and keep you up to date with notes in the Github Issue.
+
+For most teams there is a simpler on-ramp first: a ready-made GitHub
+Actions workflow (`templates/github/claude-maverick.yml`) runs Maverick
+on GitHub-hosted runners — respond to `@claude` mentions, or label an
+issue `claude-do` and `do-issue-solo` works it end-to-end. See the
+remote-execution decision matrix in
+[docs/claude-code-workers.md](docs/claude-code-workers.md) for choosing
+between the GitHub Action, Claude cloud routines, and the self-hosted
+EC2 pipeline. None of this is required — the plugin works on your local
+machine and you can ask Claude to complete tasks solo or with
+assistance.
+
+## NOTE: This project is still in Alpha and under rapid change
+
+I use this repo to build my own software and I aim to improve it every day. That means the change rate is pretty high until I get it to v1 release.
+
+- The plugin skills, agents, and hooks are solid, and the full
+  `do-issue-solo` pipeline is exercised end-to-end against real
+  repositories.
+- The `maverick` CLI carries the workflow's deterministic core
+  (coordination, state, gates, reporting) with an extensive unit-test
+  suite; the AWS worker pipeline is in maintenance mode in favour of the
+  GitHub Action on-ramp for most use cases.
+
+## Install
+
+### Plugin
+
+```sh
+# Install the plugin (registers in ~/.claude/settings.json)
+claude plugin marketplace add https://github.com/thermiteau/maverick
+claude plugin install maverick@thermite
+```
+
+### CLI
+
+This makes the `maverick` command available globally.
+
+#### Prerequisites
+
+- Python 3.10+
+- [uv](https://docs.astral.sh/uv/) — Python package manager
+- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) — Anthropic's CLI for Claude
+- Claude Code API Key
+
+```sh
+# Install system-wide from the repo
+uv tool install .
+
+# Or install in development mode
+uv tool install -e .
+```
+
+## Usage
+
+### Initialising an existing project (repo)
+
+run `/maverick:do-init` within Claude Code
+
+### Work on GitHub issues
+
+With the plugin loaded, use skills directly in Claude Code:
+
+```sh
+/maverick:do-issue-solo 42
+# Autonomous mode — Claude works end-to-end, only pausing when blocked
+
+/maverick:do-issue-guided 42
+# Guided mode — Claude pauses for approval at design and plan phases
+
+/maverick:do-maverick-alignment
+# Audit a codebase against Maverick standards
+
+/maverick:do-adopt recommend
+# Recommend (or, without 'recommend', implement) missing best practices
+
+/maverick:do-upskill logging
+# Generate a project-specific implementation skill for one topic
+```
+
+Or skip the terminal entirely: copy
+`templates/github/claude-maverick.yml` into `.github/workflows/`, then
+label any issue `claude-do` and Maverick completes it on a GitHub-hosted
+runner — design, tasks, implementation, docs and security gates, PR,
+review, and merge.
+
+## Development
+
+```sh
+# Run unit tests
+uv sync --extra test && uv run pytest tests/unit/ -v
+```
+
+CI runs automatically on pushes and PRs to `main` via GitHub Actions.
+
+## License
+
+Apache License 2.0

maverick_harness-5.0.0/pyproject.toml

@@ -0,0 +1,44 @@
+[build-system]
+requires = ["setuptools>=64"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "maverick-harness"
+version = "5.0.0"
+description = "Claude Code plugin that enables autonomous AI development while maintaining best practices"
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "boto3",
+    "jinja2>=3.1",
+    "pyjwt[crypto]>=2.8",
+    "pyright>=1.1.408",
+    "pyyaml>=6.0",
+    "ruff>=0.8",
+]
+
+[project.optional-dependencies]
+test = ["pytest>=8.0"]
+
+[project.scripts]
+maverick = "maverick.cli:main"
+
+[tool.ruff]
+target-version = "py310"
+line-length = 100
+src = ["src", "scripts", "tests"]
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "C4"]
+ignore = ["E501"]
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+"maverick.cloud_init" = ["**/*.yaml"]
+
+[tool.uv.workspace]
+members = [
+    "prototyping/my-python-app",
+]

maverick_harness-5.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

maverick_harness-5.0.0/src/maverick/agents/agent-code-reviewer/config.py

@@ -0,0 +1,34 @@
+from maverick.models import AgentConfig, ClaudeAgentOptions
+from maverick.names import (
+    AGENT_CODE_REVIEWER,
+    MAV_BP_CODE_REVIEW,
+    MAV_BP_OPERABILITY,
+    MAV_BP_TESTING,
+    MAV_SCOPE_BOUNDARIES,
+)
+
+CONFIG = AgentConfig(
+    name=AGENT_CODE_REVIEWER,
+    description=(
+        "Autonomous code reviewer that performs two-stage review — spec compliance"
+        " first, then code quality (correctness, test coverage, maintainability)."
+        " Security is out of scope; do-cybersecurity-review handles that as a"
+        " mandatory pre-push gate. Dispatched after completing implementation"
+        " steps or before creating PRs."
+    ),
+    # A reviewer that can fix what it reviews stops being a gate: read-only.
+    read_only=True,
+    skills=[
+        MAV_BP_CODE_REVIEW,
+        MAV_BP_OPERABILITY,
+        MAV_BP_TESTING,
+        MAV_SCOPE_BOUNDARIES,
+    ],
+    claude=ClaudeAgentOptions(
+        color="yellow",
+        # The merge gate must not inherit whatever model the caller runs — a
+        # cost-conscious session would silently weaken the highest-stakes
+        # judgment in the system. Pin a strong model explicitly.
+        model="opus",
+    ),
+)