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 an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget…
MITAuto-check passed
Install Percom Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-submission .claude/skills/percom-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 "percom-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-submission into .claude/skills/percom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-submission .agents/skills/percom-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 "percom-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-submission into .agents/skills/percom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-submission .cursor/skills/percom-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 "percom-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-submission into .cursor/skills/percom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-submission .gemini/skills/percom-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 "percom-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-submission into .gemini/skills/percom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-submission .github/skills/percom-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 "percom-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-submission into .github/skills/percom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-submission .opencode/skills/percom-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 "percom-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-submission into .opencode/skills/percom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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
percom-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 736 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget…
- Works in 6 steps: Freeze the body early; references can… → Register title/abstract/authors/topics… → Build the anonymized dataset/artifact… → …
- Auditing an IEEE PerCom research-track submission for HotCRP readiness
- SKILL.md covers The two-step deadline, Format and page budget, Double-blind sweep and Open data and human subjects…, plus 4 more sections
- Calls pdftotext
What it does
Percom Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication, and desk-reject triage before the AoE cutoff.
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 an IEEE PerCom research-track submission for HotCRP readiness
- Covering the mandatory paper-registration step
- The IEEEtran 9+1 two-column page budget
- Double-blind anonymization
Example prompts
- “/percom-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the body early; references can churn, the argument cannot.
- Register title/abstract/authors/topics well before the registration cutoff.
- Build the anonymized dataset/artifact link and place the open-data plan and ethics note in the
- Run the mechanical anonymity checks on the final PDF and the final archive, not drafts.
- Fill every HotCRP field — topics that match your evidence, conflicts for every coauthor's
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
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
Percom Submission loads about 1.6k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 736 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). 736 words, ~1,598 tokens.
Download SKILL.mdSave it as
.claude/skills/percom-submission/SKILL.md (or your agent's skills folder).- name
- percom-submission
- description
- Use when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication, and desk-reject triage before the AoE cutoff.
PerCom Submission
Run this audit before uploading to the PerCom HotCRP site (percom2027.hotcrp.com for the current
cycle). PerCom research papers publish in IEEE Xplore and are reviewed double-blind, so the
submission must be both anonymous and complete on its own — the bounded rebuttal cannot add new
experiments later. Every number below was read from the PerCom 2027 Call for Papers and Dates pages
on 2026-07-09 via search renderings of the percom.org URLs (see
resources/official-source-map.md); treat them as a one-cycle snapshot and reopen the live call
first.
The two-step deadline
PerCom separates paper registration from paper submission, and both are AoE:
- Registration locks in title, abstract, authors, and topic areas about a week early (PerCom 2027: 4 September 2026). Miss it and the system will not accept the PDF later.
- Submission uploads the anonymized PDF (PerCom 2027: 11 September 2026, 23:59 AoE).
Register with the real title and abstract, not a placeholder — the abstract drives TPC bidding, and a registered abstract that diverges from the final paper quietly worsens your reviewer match.
Format and page budget
- IEEEtran,
\documentclass[10pt, conference, compsocconf]{IEEEtran}, US-letter, two-column — the IEEE Computer Society conference format. This is the IEEE path, not ACMacmart. - Page budget (verify per cycle): at most 9 pages of technical content — text, figures, tables, and appendices all count — plus up to 1 additional page for references only. There is no unlimited appendix inside the paper; anything reviewers must read to judge it lives in the 9.
- Margins, font, and column geometry are fixed by the template; editorial compression, not template tampering, is how you recover space. A shrunk font or narrowed margin is a named desk-reject ground at IEEE venues.
Double-blind sweep
PerCom runs double-blind review: authors anonymize in good faith and cite their own prior work in the third person (do not omit it — omission is itself a tell). Because ubicomp papers lean on datasets, testbeds, and deployments, the leak surface is wide:
# Mechanical pass on the submission PDF and any anonymized dataset/artifact archive
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|ieee-dataport|zenodo\.org/record|acknowledg|IRB|university' | head
unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head
grep -rni 'our (lab|testbed|deployment)|@[a-z0-9.]*\.edu' artifact/ --include='*.md' | headThe ubicomp-specific leaks: a testbed or smart-home named after your lab, a photo of the sensor rig showing a building or a face, a dataset link pointing at a personal repository, an IRB protocol number tied to your institution, and a "we deployed in our department" phrasing. Re-host datasets behind an anonymizing link before upload.
Open data and human subjects at submission time
PerCom's community expects a credible data story and, for human-subjects sensing, an ethics story:
- State an open-data plan: what dataset exists, whether/where it will be released after acceptance, and — for anything you cannot share (privacy, IRB limits) — exactly why.
- Provide an anonymized dataset/code link or upload anonymized material for the reviewers.
- State IRB/ethics approval and consent for human-subjects data collection, and the de-identification done — a missing ethics note is a scored weakness, not a neutral omission.
Show full SKILL.md (277 more words)Show less
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Over 9 pages of technical content | Desk-reject-grade | Cut or move to the dataset/artifact; the reference page does not absorb body text |
Template altered (10pt/compsocconf changed, margins, shrunk font) | Named desk-reject ground | Recompile clean, recover space editorially |
| Identity leak in PDF, dataset link, testbed name, or a photo | Anonymity violation | Re-anonymize and re-host; scrub PDF metadata |
| Own prior work omitted for "anonymity" | Double-blind done wrong | Restore the citation in the third person |
| Abstract/authors not registered by the earlier date | No submission slot exists | Nothing fixes this post-AoE — calendar it now |
| No open-data plan, no ethics note for human data | Scored against the paper | Add the plan + IRB/consent statement |
| Same study under review elsewhere | Dual-submission exposure | Withdraw one venue; verify the current concurrent-submission wording |
Final-week order of operations
- Freeze the body early; references can churn, the argument cannot.
- Register title/abstract/authors/topics well before the registration cutoff.
- Build the anonymized dataset/artifact link and place the open-data plan and ethics note in the paper.
- Run the mechanical anonymity checks on the final PDF and the final archive, not drafts.
- Fill every HotCRP field — topics that match your evidence, conflicts for every coauthor's institution and recent collaborators — a day early; late conflicts are the classic midnight failure.
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
Reverify each cycle
- The exact dates, the rebuttal window, and the early-rejection wording.
- The page budget and the required IEEEtran options (PerCom 2027 posts 9+1 with
compsocconf). - WiP/demo/industry/workshop deadlines (separate), dual-submission wording, whether a reproducibility track runs, and any AI-disclosure rule — all cycle-volatile.
Output format
[PerCom submission status] ready / blocked / needs work
[Registration] title/abstract/authors/topics locked by the earlier deadline? yes/no
[Format] pages used (body/refs), IEEEtran compsocconf compliance
[Anonymity] clean / leaks: <where>
[Open data + ethics] dataset link present? open-data plan? IRB/consent stated?
[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 PerCom-Skills/skills/percom-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Percom 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 |
|---|---|---|---|---|---|---|
| Percom 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 | |
| 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 | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT |
Similar skills
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.
Qms Audit Expert
davila7/claude-code-templates
Senior QMS Audit Expert for internal and external quality management system auditing.
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 Percom Submission
What does Percom Submission do?
A skill your agent uses when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget…. Percom Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication, and desk-reject triage before the AoE cutoff.
When should I use Percom Submission?
Percom Submission fits situations like: auditing an IEEE PerCom research-track submission for HotCRP readiness; covering the mandatory paper-registration step; the IEEEtran 9+1 two-column page budget; double-blind anonymization.
How do I install Percom Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-submission -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-submission in your project. Claude Code loads it when a task matches its description.
How do I install Percom Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-submission -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-submission in your project. Codex loads it when a task matches its description.
Can I use Percom 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 percom-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/percom-submission, .gemini/skills/percom-submission, .github/skills/percom-submission and .opencode/skills/percom-submission in your project.
What does Percom Submission need to run?
Going by SKILL.md and its folder, Percom Submission needs the command-line tools its instructions call (pdftotext).
Does Percom 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 Percom 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 Percom Submission use?
Percom 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 Percom 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 Percom Submission?
Skills that share tags, products or a category with Percom Submission: Production Audit (affaan-m/ECC, 277k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars), Geo Audit (sickn33/agentic-awesome-skills, 47k stars) and OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Percom 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.