Metadata-Version: 2.5
Name: pragmatic-audit
Version: 0.1.0
Summary: Audit a repository against The Pragmatic Programmer, and give agents a practical standard to code by.
Project-URL: Homepage, https://cobaltchaser.github.io/pragmatic-audit/
Project-URL: Documentation, https://cobaltchaser.github.io/pragmatic-audit/
Project-URL: Repository, https://github.com/CobaltChaser/pragmatic-audit
Project-URL: Issues, https://github.com/CobaltChaser/pragmatic-audit/issues
Project-URL: Changelog, https://github.com/CobaltChaser/pragmatic-audit/blob/main/CHANGELOG.md
Author: Himanshu Sharma
License: 
                                         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 2026 Himanshu Sharma
        
           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.
License-File: LICENSE
License-File: NOTICE
Keywords: ai-agents,code-quality,code-review,developer-tools,pragmatic-programmer,static-analysis
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Topic :: Software Development :: Quality Assurance
Requires-Python: >=3.11
Description-Content-Type: text/markdown

<div align="center">

<img src="docs/assets/hero.svg" alt="pragmatic-audit — ship code that is easy to change, even when an agent wrote it" width="100%">

<br>

[![CI](https://github.com/CobaltChaser/pragmatic-audit/actions/workflows/ci.yml/badge.svg)](https://github.com/CobaltChaser/pragmatic-audit/actions/workflows/ci.yml)
[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-3776AB?logo=python&logoColor=white)](https://www.python.org/)
[![PyPI](https://img.shields.io/pypi/v/pragmatic-audit.svg)](https://pypi.org/project/pragmatic-audit/)
[![Zero dependencies](https://img.shields.io/badge/runtime-zero%20dependencies-2ea44f)](#what-it-will-not-do)
[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
[![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen)](CONTRIBUTING.md)
[![Agent Skills](https://img.shields.io/badge/Agent%20Skills-compatible-6f42c1)](docs/agent-skill.md)

</div>

<h1 align="center">pragmatic-audit</h1>

<p align="center"><strong>Code-quality audits for AI-generated code.</strong> A zero-dependency CLI and agent skill that check a repository against <em>The Pragmatic Programmer</em>.</p>

AI made writing code cheap. Changing it is still expensive.

`pragmatic-audit` checks a repository against the durable principles from *The Pragmatic Programmer* — DRY, orthogonality, contracts, resource ownership, external configuration, tests, and more — then hands the judgment calls to your agent with a focused review packet. Read the [project site](https://cobaltchaser.github.io/pragmatic-audit/) for the [AI code audit workflow](https://cobaltchaser.github.io/pragmatic-audit/audit-ai-generated-code.html) and the [Pragmatic Programmer checklist](https://cobaltchaser.github.io/pragmatic-audit/pragmatic-programmer-checklist.html).

It is for humans reviewing agent output, and for agents that need to write code worth keeping.

<img src="docs/assets/terminal-audit.svg" alt="Terminal output from a pragmatic-audit run" width="100%">

## Why this matters in the agentic era

Agents can produce code faster than humans can review it. They also copy patterns — including bad ones — at scale. Prototypes that were meant to be thrown away become production systems, and the small compromises compound.

The bottleneck has moved. It is no longer how fast a team can type. It is how cheaply the code can change next week.

Principles are portable guardrails. They survive model upgrades, framework churn, and team changes. A deterministic audit gives humans and agents the same vocabulary for a review:

- **DRY** asks whether one piece of knowledge has one authoritative home.
- **Orthogonality** asks whether a change stays local.
- **Contracts** ask whether a boundary fails loudly or lies quietly.
- **Resource ownership** asks who closes what they opened.
- **Tests** ask whether behavior is pinned down or merely exercised.

`pragmatic-audit` finds the mechanical violations. The bundled skill teaches an agent how to reason about the rest.

## What you get

| | |
|---|---|
| **Audit** | A fast, offline scan with file-and-line findings, severity, confidence, and a concrete fix. 20 core checks, plus 3 opt-in history checks. |
| **Explain** | Every finding names the principle and tip it comes from. The report separates mechanical findings from questions that need human judgment. |
| **Coach** | `--agent-packet` writes a JSON and Markdown briefing your agent can use to review the code, confirm or dismiss findings, and propose the smallest useful change. |

No network. No telemetry. No LLM calls inside the CLI. No dependencies outside the Python standard library.

## Quick start

Run it against any repository without installing anything:

```bash
git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git /tmp/pragmatic-audit
cd /tmp/pragmatic-audit && python3 -m pragmatic_audit /path/to/repo
```

Or install the CLI from PyPI:

```bash
pip install pragmatic-audit
pragmatic-audit .
```

With `pipx`:

```bash
pipx install pragmatic-audit
pragmatic-audit .
```

Common modes:

```bash
# Human-readable report
pragmatic-audit .

# Stable JSON for CI and agents
pragmatic-audit . --format json

# Findings plus a review packet for your coding agent
pragmatic-audit . --agent-packet

# Fail the build on high-severity findings
pragmatic-audit . --ci --fail-on high
```

Python 3.11 or newer. Nothing else.

## Install the agent skill

The skill lives in [`skills/pragmatic-programmer`](skills/pragmatic-programmer). Every command below is repeatable and self-cleaning.

### Claude Code

```bash
rm -rf ~/.cache/pragmatic-audit && git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git ~/.cache/pragmatic-audit && mkdir -p ~/.claude/skills && cp -R ~/.cache/pragmatic-audit/skills/pragmatic-programmer ~/.claude/skills/
```

### Claude Cowork / claude.ai

```bash
rm -rf ~/.cache/pragmatic-audit && git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git ~/.cache/pragmatic-audit && cd ~/.cache/pragmatic-audit/skills && zip -r ~/Downloads/pragmatic-programmer.zip pragmatic-programmer
```

Then open **Customize → Skills → Upload** and select `pragmatic-programmer.zip`.

### ChatGPT Work / CoWork

```bash
rm -rf ~/.cache/pragmatic-audit && git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git ~/.cache/pragmatic-audit && cd ~/.cache/pragmatic-audit/skills && zip -r ~/Downloads/pragmatic-programmer.zip pragmatic-programmer
```

Then open **Plugins → Skills → Create → Upload from your computer** and select the ZIP.

For local Codex:

```bash
rm -rf ~/.cache/pragmatic-audit && git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git ~/.cache/pragmatic-audit && mkdir -p ~/.codex/skills && cp -R ~/.cache/pragmatic-audit/skills/pragmatic-programmer ~/.codex/skills/
```

### OpenCode

```bash
rm -rf ~/.cache/pragmatic-audit && git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git ~/.cache/pragmatic-audit && mkdir -p ~/.config/opencode/skills && cp -R ~/.cache/pragmatic-audit/skills/pragmatic-programmer ~/.config/opencode/skills/
```

Project-local variant:

```bash
mkdir -p .opencode/skills && cp -R /path/to/pragmatic-audit/skills/pragmatic-programmer .opencode/skills/
```

### Everything else (Agent Skills standard)

```bash
rm -rf ~/.cache/pragmatic-audit && git clone --depth 1 https://github.com/CobaltChaser/pragmatic-audit.git ~/.cache/pragmatic-audit && mkdir -p ~/.agents/skills && cp -R ~/.cache/pragmatic-audit/skills/pragmatic-programmer ~/.agents/skills/
```

Host notes:

- Claude Code reads `~/.claude/skills/` and `.claude/skills/`.
- OpenCode reads `~/.config/opencode/skills/`, `~/.claude/skills/`, `~/.agents/skills/`, and their project equivalents.
- Codex reads local skills from `~/.codex/skills/`. ChatGPT workspace skills are uploaded through the UI.
- Cursor and other compatible hosts can use `~/.agents/skills/` or their documented local skill directory.
- Keep `SKILL.md` at the root of the skill folder. The folder name must match the skill name.

See [docs/agent-skill.md](docs/agent-skill.md) for invocation examples and compatibility notes.

## Use it in CI

```yaml
name: pragmatic-audit

on:
  push:
  pull_request:

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.12"
      - run: pipx install pragmatic-audit
      - run: pragmatic-audit . --ci --fail-on high --format markdown --output pragmatic-audit.md
      - uses: actions/upload-artifact@v4
        if: always()
        with:
          name: pragmatic-audit
          path: pragmatic-audit.md
```

Exit codes:

| Code | Meaning |
|---|---|
| `0` | Audit completed, gate passed |
| `1` | Audit completed, gate failed |
| `2` | Invalid usage or unreadable path |
| `3` | Internal error |

The gate is opt-in. By default the CLI reports and exits `0`. Use `--fail-on medium` when the codebase is ready for a stricter ratchet.

## The 20 core checks

<details>
<summary><strong>Open the rule table</strong></summary>

<br>

| Rule | Principle | What it catches |
|---|---|---|
| `PP-DRY` | Don't repeat yourself | Duplicated normalized blocks of 6+ lines and duplicate functions |
| `PP-CONFIG` | External configuration | Hardcoded secrets, environment URLs, absolute paths, and non-local IPs |
| `PP-MAGIC` | Policy is metadata | Unexplained numeric thresholds in comparisons |
| `PP-ORTHO` | Orthogonality | Import cycles and modules with excessive internal fan-out |
| `PP-GLOBALS` | Avoid global data | Module-level mutable state, `global`, and mutable defaults |
| `PP-TRAINWRECK` | Decoupled code | Call chains that reach through three or more objects |
| `PP-INHERIT` | Composition over inheritance | Inheritance depth over two |
| `PP-CONTRACTS` | Design with contracts | Empty catches, swallowed errors, and bare `except` |
| `PP-RESOURCES` | Resource ownership | Acquired resources without a guaranteed release path |
| `PP-COINCIDENCE` | Rely on reliable things | Mutable defaults, float equality, loose JS equality, and stale `var` |
| `PP-COMPLEXITY` | Good design is easier to change | Long functions, deep nesting, high branch count, and too many parameters |
| `PP-NAMING` | Express intent | Single-letter and generic names, and vague boolean names |
| `PP-COMMENTS` | Good code is its own documentation | Commented-out code blocks |
| `PP-BROKEN-WINDOWS` | Fix bad code when you see it | Skip markers, unexplained suppressions, and TODO/FIXME density |
| `PP-TESTS` | Design to test | Missing tests, thin coverage, and assertion-free tests |
| `PP-TEST-HYGIENE` | A good test is a good neighbor | Sleeps, real network calls, and nondeterministic input in tests |
| `PP-AUTOMATION` | Automate the routine | Missing CI, task automation, and unscripted release steps |
| `PP-VCS` | Version control everything | Missing git, missing `.gitignore`, tracked secrets, and large files |
| `PP-E2E` | Build end-to-end | Unit-only suites with no smoke or end-to-end path |
| `PP-DOCS` | Documentation lives with the code | Missing or unhelpful README documentation |

</details>

Opt-in history and architecture checks:

| Rule | Principle | What it catches |
|---|---|---|
| `PP-SMALL-STEPS` | Small reversible steps | Commits touching more than 30 files or 1,000 lines |
| `PP-REVERSIBILITY` | There are no final decisions | Vendor SDKs spread across modules without an adapter boundary |
| `PP-SHARED-STATE` | Avoid shared mutable state | Mutable module state in files that use concurrency |

Enable them with `--include-history` or `--all`.

Full rationale, examples, false positives, and tuning: [docs/rules.md](docs/rules.md).

## Hybrid by design

Static analysis is good at finding mechanical violations. It is bad at judging design.

This tool does not pretend otherwise.

1. **The scanner** produces deterministic findings with locations and fixes. It reads Python and JavaScript/TypeScript structurally, and uses conservative text heuristics for Go, Java, Ruby, PHP, Rust, and others.
2. **The report** adds a manual review queue: tracer bullets, boundary contracts, orthogonality, domain language, reversibility, test design, and speculative code.
3. **The packet** gives an agent the evidence and a question set. The agent must open the files, confirm or dismiss each finding, and report only the few changes that most improve changeability.

```bash
pragmatic-audit . --agent-packet
```

That writes `pragmatic-audit.packet.json` and `pragmatic-audit.packet.md` in the current directory. Neither file is required for normal use; both are designed to be pasted into an agent session.

## What it will not do

- It will not auto-fix code.
- It will not make network requests or call an LLM.
- It will not replace your linter, type checker, test runner, or security scanner.
- It will not produce a definitive quality score. The number is directional and always shown next to raw counts.
- It will not understand every framework’s conventions. False positives are expected; dismiss them with a reason or tune the rule.
- It will not prove that code is correct.

Treat every finding as a hypothesis. Read the code before changing it.

## Example report

The bundled bad repository produces a real report: [examples/report.md](examples/report.md).

<img src="docs/assets/report-preview.svg" alt="Preview of a pragmatic-audit report" width="100%">

The examples are deliberately small and are used by the test suite:

```bash
pragmatic-audit examples/bad-repo
pragmatic-audit examples/good-repo
```

## Tuning

Create `.pragmatic-audit.toml` at the repository root:

```toml
[scan]
exclude = ["generated", "public/vendor", "*.min.js"]
languages = ["python", "javascript", "typescript"]

[thresholds]
long_function = 60
deep_nesting = 4
max_params = 5
test_ratio = 0.3

[ignore]
rules = ["PP-MAGIC"]
paths = ["migrations/**"]

[ci]
fail_on = "high"
min_confidence = "medium"
```

Suppress a single line when the finding is genuinely wrong:

```python
if len(items) > 42:  # pragmatic-audit: ignore PP-MAGIC pagination boundary from the API contract
```

Suppress a file when the whole file is a known exception:

```python
# pragmatic-audit: ignore-file PP-GLOBALS this module is the state owner
```

Every suppression needs a written reason. A suppression without a reason is a broken window.

## Self-audited

This repository runs `pragmatic-audit` on itself in CI, and the test suite includes the rules it ships. The current self-audit report is [examples/self-audit.md](examples/self-audit.md), generated by `scripts/self_audit.sh`.

The tool is not expected to score 100. It is expected to show its own trade-offs honestly, including deliberate exceptions and false positives.

## Contributing

**PRs are open.** This project gets better when more people encode the principles they actually use. Rule proposals, false-positive reports, new language patterns, docs fixes, and examples are all welcome.

Good first contributions:

- Add a language pattern to an existing rule, with a positive and negative fixture.
- Improve a rule description or a fix suggestion.
- Add a false-positive case that the current tests miss.
- Make an example repository more realistic.
- Tighten the docs.

Read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request. The short version:

```bash
python3 -m unittest discover -s tests -v
python3 -m compileall pragmatic_audit
python3 -m pragmatic_audit . --ci --fail-on high
```

No new runtime dependencies. Every rule needs a test. Every behavior claim needs a test or a code link.

- [Rule proposal template](.github/ISSUE_TEMPLATE/rule_proposal.yml)
- [Bug report template](.github/ISSUE_TEMPLATE/bug_report.yml)
- [Code of conduct](CODE_OF_CONDUCT.md)
- [Security policy](SECURITY.md)

## License

Apache-2.0. Use it at work, in commercial products, and in closed-source repositories. Keep the copyright, license, and [`NOTICE`](NOTICE) file, and state significant changes.

Full terms: [LICENSE](LICENSE).

## Credits

*The Pragmatic Programmer, 20th Anniversary Edition* is by David Thomas and Andrew Hunt. This project is an independent, unofficial tool. Tip names and numbers are referenced descriptively with attribution. No book text is reproduced. The project is not affiliated with the authors or The Pragmatic Programmers, LLC.

The audit text, prompts, and documentation in this repository are original paraphrases and implementations.
