Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
A skill your agent uses when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application /…
MITAuto-check passed
Install Cav Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-submission --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/CAV-Skills/skills/cav-submission .claude/skills/cav-submission && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cav-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submission into .claude/skills/cav-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-submission", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submissionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-submission --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/CAV-Skills/skills/cav-submission .agents/skills/cav-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cav-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submission into .agents/skills/cav-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-submission", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-submission --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/CAV-Skills/skills/cav-submission .cursor/skills/cav-submission && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cav-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submission into .cursor/skills/cav-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-submission", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path CAV-Skills/skills/cav-submission--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-submission --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/CAV-Skills/skills/cav-submission .gemini/skills/cav-submission && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cav-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submission into .gemini/skills/cav-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-submission", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-submissionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/CAV-Skills/skills/cav-submission .github/skills/cav-submission && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cav-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submission into .github/skills/cav-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-submission", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-submission --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/CAV-Skills/skills/cav-submission .opencode/skills/cav-submission && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cav-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-submission into .opencode/skills/cav-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-submission", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cav-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 725 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application /…
- Works in 6 steps: Confirm the category and its page limit… → Freeze the body early; the… → Build the artifact and, for anonymized… → …
- Auditing a CAV (Computer Aided Verification) submission for portal readiness
- SKILL.md covers Pick the right category first, Format and page budget, Double-blind sweep (Regular… and Artifact intent at submission…, plus 4 more sections
- Calls pdftotext
What it does
Cav Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Auditing a CAV (Computer Aided Verification) submission for portal readiness
- Covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies)
- The LNCS page limits
- The per-category anonymization matrix
Example prompts
- “/cav-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Confirm the category and its page limit and anonymity rule against the live CFP.
- Freeze the body early; the theorem/algorithm and the benchmark table are the argument.
- Build the artifact and, for anonymized categories, its anonymized copy; set artifact intent.
- Run the mechanical anonymity sweep on the final PDF and archive (anonymized categories only).
- Fill every portal field — category, topics, conflicts for every co-author's institution — a day
- Confirm the portal (EasyChair or HotCRP — verify the live link) and re-download the uploaded
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pdftotext
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cav Submission loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 725 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 725 words, ~1,599 tokens.
Download SKILL.mdSave it as
.claude/skills/cav-submission/SKILL.md (or your agent's skills folder).- name
- cav-submission
- description
- Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.
CAV Submission
Run this audit before uploading to the CAV submission portal. CAV research papers are published
open access as Springer LNCS chapters, and the submission is judged by a two-stage review, so
the category you pick, the LNCS format, and the anonymization rule for that category all have to be
right before the deadline. Every number below was read from the CAV 2026 Call for Papers on
2026-07-09 via search renderings of the i-cav.org URLs (see
resources/official-source-map.md); treat them as a one-cycle snapshot and reopen the live CFP
first.
Pick the right category first
CAV 2026 solicits four categories, and the category sets both the page limit and the anonymity rule:
| Category | Page limit (LNCS, excl. refs + appendix) | Anonymized? | Fits |
|---|---|---|---|
| Regular Paper | 18 pages | Yes (double-blind) | A new technique/algorithm with a formal contribution |
| Short Tool Paper | 10 pages | No | A usable, downloadable verification tool on standard benchmarks |
| Short Application Paper | 10 pages | Yes (double-blind) | Applying verification to a concrete problem/system |
| Industrial Experience Report & Case Study | 10 pages | No | A real-world/industrial verification experience |
The anonymization split is unusual and cycle-volatile — verify it on the current CFP. The logic: a tool paper that hid its tool's name would be unreviewable, so tool and industrial papers are not anonymized; regular and application papers are.
Format and page budget
- LNCS
llncsdocument class, single column, unmodified. This is the Springer path — do not carry an ACMacmartor an IEEEtran double-column habit across from a sibling venue. - Page limits exclude references and appendices. A clearly marked appendix is allowed, but
reviewers are not obliged to read it — so nothing that decides acceptance may live only in the
appendix (see
cav-supplementary). - Margins, font, and spacing are fixed by
llncs; recover space by editing, not by tampering with the template.
Double-blind sweep (Regular and Application papers)
For the anonymized categories, CAV runs double-blind review, and verification papers leak identity through tool names, repositories, and benchmark artifacts:
# Mechanical pass on an anonymized submission PDF and any artifact archive
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org|our (tool|solver|prover)|acknowledg|grant' | head
unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | headThe verification-specific leaks: a solver named after your group, a benchmark path revealing a cluster/username, a tool repository URL in the evaluation, and an acknowledgement of a grant that identifies the lab. Re-host anonymized artifacts behind an anonymizing service before upload. For tool and industrial papers, this sweep does not apply — the tool's identity is expected.
Artifact intent at submission time
CAV asks authors to declare artifact intent at submission — whether you plan to submit an
artifact to the AEC if the paper is accepted — and this information is shared with reviewers.
Decide early: an artifact-backed claim reads as stronger. Artifact evaluation itself is
post-notification, invited, and not a condition of acceptance (see cav-artifact-evaluation).
Show full SKILL.md (290 more words)Show less
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Wrong category (tool work filed as Regular, or vice versa) | Mis-routed review | Re-file in the correct category before the deadline; the page limit and anonymity change |
| Main text over the page limit | Desk-reject-grade | Cut or move to the (optional-to-read) appendix; refs/appendix do not absorb body text |
Non-LNCS template or altered llncs | Format violation | Recompile clean in llncs, recover space editorially |
| Identity leak in an anonymized (Regular/Application) paper | Anonymity violation | Re-anonymize PDF, tool name, and artifact; re-host |
| Anonymized a Tool/Industrial paper by mistake | Reviewability problem | These are not double-blind — restore tool identity |
| No artifact-intent declaration | Missing signal to reviewers | Set it in the portal; decide the AEC plan now |
| Same work under review elsewhere | Dual-submission exposure | Withdraw one venue; verify the current concurrent-submission wording |
Final-week order of operations
- Confirm the category and its page limit and anonymity rule against the live CFP.
- Freeze the body early; the theorem/algorithm and the benchmark table are the argument.
- Build the artifact and, for anonymized categories, its anonymized copy; set artifact intent.
- Run the mechanical anonymity sweep on the final PDF and archive (anonymized categories only).
- Fill every portal field — category, topics, conflicts for every co-author's institution — a day early; late conflicts are the classic midnight failure.
- Confirm the portal (EasyChair or HotCRP — verify the live link) and re-download the uploaded PDF to confirm it is the file you meant.
Reverify each cycle
- Whether a separate abstract/registration deadline precedes the paper deadline (待核实 for 2026; only the paper deadline was confirmed).
- The per-category page limits, the anonymization matrix, and which LNCS template revision is required.
- The submission portal (EasyChair vs. HotCRP), two-stage-review mechanics, and dual-submission wording — all cycle-volatile.
Output format
[CAV submission status] ready / blocked / needs work
[Category] Regular / Short Tool / Short Application / Industrial — matches the contribution? yes/no
[Format] pages used (body), LNCS llncs compliance
[Anonymity] required for this category? yes/no -> clean / leaks: <where>
[Artifact intent] declared? AEC plan noted?
[Fix queue] <ordered, with owners and dates before the AoE cutoff>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in CAV-Skills/skills/cav-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cav Submission next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cav Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Ito Computeaffaan-m/ECC | 277k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT | |
| OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute | 75k | — | ~733 | Automated safety check: Pass | MIT |
Similar skills
Ito Compute
affaan-m/ECC
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately…
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Cav Submission
What does Cav Submission do?
A skill your agent uses when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application /…. Cav Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.
When should I use Cav Submission?
Cav Submission fits situations like: auditing a CAV (Computer Aided Verification) submission for portal readiness; covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies); the LNCS page limits; the per-category anonymization matrix.
How do I install Cav Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a claude-code`. Or copy the skill folder (CAV-Skills/skills/cav-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cav-submission in your project. Claude Code loads it when a task matches its description.
How do I install Cav Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a codex`. Or copy the skill folder (CAV-Skills/skills/cav-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cav-submission in your project. Codex loads it when a task matches its description.
Can I use Cav Submission in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cav-submission, .gemini/skills/cav-submission, .github/skills/cav-submission and .opencode/skills/cav-submission in your project.
What does Cav Submission need to run?
Going by SKILL.md and its folder, Cav Submission needs the command-line tools its instructions call (pdftotext).
Does Cav Submission access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cav Submission safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cav Submission use?
Cav Submission is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cav Submission use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cav Submission?
Skills that share tags, products or a category with Cav Submission: Production Audit (affaan-m/ECC, 277k stars), Ito Compute (affaan-m/ECC, 277k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars) and Geo Audit (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cav Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.