audit-report

Files (1)

• SKILL.md

SKILL.md (first lines)

Generate a combined PDF audit report from all markdown files in the `audit/` directory.

## Step 1: Check checklist completion

Read `audit/AUDIT-CHECKLIST.md`. If it does not exist, stop and report that no
checklist was found.

Scan the `## Progress` section for any unchecked items (`- [ ]`). If any are
found, stop and explain which items are still incomplete and that the PDF will
not be generated until all audit items are checked off.

## Step 2: Locate audit files

Look for the following in the `audit/` directory:
- `AUDIT-CHECKLIST.md` — progress tracker (used for the completeness check and
  severity totals only; it is NOT included in the PDF)
- `audit-*.md` — individual audit reports (include in filename order)
- `tob-maturity.md`, `tob-prep.md` — Trail of Bits output (selected sections
  only go into the appendices, if present)

If no `audit-*.md` files are found, stop and report the error.

## Step 3: Write a CSS stylesheet

Write the following stylesheet to `/tmp/audit-report.css`:

```css
@page {
    size: A4;
    margin: 2cm;
}

body {
    font-family: "DejaVu Sans", sans-serif;
    font-size: 11pt;
    line-height: 1.5;
    color: #1a1a1a;
}

h1 { font-size: 2em; border-bottom: 2px solid #333; padding-bottom: 0.3em; }
h2 { font-size: 1.4em; border-bottom: 1px solid #ccc; padding-bottom: 0.2em; margin-top: 2em; }
h3 { font-size: 1.1em; margin-top: 1.5em; }

code {
    font-family: "DejaVu Sans Mono", monospace;
    font-size: 0.9em;
    background: #f4f4f4;
    padding: 0.1em 0.3em;
    border-radius: 3px;
    overflow-wrap: anywhere;
}

pre {
    background: #f4f4f4;
    border-left: 3px solid #ccc;
    padding: 1em;
    white-space: pre-wrap;
    overflow-wrap: anywhere;
    font-size: 0.85em;
}

pre code {
    background: none;
    padding: 0;
    white-space: pre-wrap;
}

table {
    border-collapse: collapse;
    width: 100%;
    margin: 1em 0;
}

th, td {
    border: 1px solid #ccc;
    padding: 0.4em 0.8em;
    text-align: left;
    overflow-wrap: anywhere;
}

th { background: #f0f0f0; font-weight: bold; }
tr:nth-child(even) { background: #fafafa; }

hr { border: none; border-top: 1px solid #ccc; margin: 2em 0; }

.page-break { page-break-before: always; }
```

## Step 4: Build the combined markdown document

Never include any `AUDIT-CHECKLIST.md` (current or archived) in the combined
document.

Build a single combined markdown document in this order:

1. **Report header** (generated):

   Read the metadata lines (`**Date:**`, `**Auditor:**`, `**Scope:**`,
   `**Repository:**`, `**Commit:**`) from the top of every current-round
   `audit-*.md` file and produce:

   ```
   | | |
   |---|---|
   | **Report date** | <today, YYYY-MM-DD> |
   | **Audit date(s)** | <distinct dates, ascending, comma-separated> |
   | **Auditor** | <distinct auditors> |
   | **Repository** | <distinct repository URLs> |
   | **Commit** | <distinct full commit hashes> |
   | **Scope** | <every scope, comma-separated, in report filename order> |
   | **Audit round** | <N, where N = 1 + number of audit/round-*/ directories> |
   ```

   For any field where reports disagree, list every distinct value (one per
   line, separated with `<br>`). Do NOT add a top-level `#` title here — pandoc
   renders the document title from the `--metadata title` option.

2. **Findings summary** (generated): a `# Findings Summary` section containing:

From jcvernaleo/llm-scripts, ISC.

More from jcvernaleo/llm-scripts