Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when auditing a TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool…
Install Tacas Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-submission .claude/skills/tacas-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 "tacas-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-submission into .claude/skills/tacas-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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/TACAS-Skills/skills/tacas-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 tacas-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-submission .agents/skills/tacas-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 "tacas-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-submission into .agents/skills/tacas-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 tacas-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-submission .cursor/skills/tacas-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 "tacas-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-submission into .cursor/skills/tacas-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 TACAS-Skills/skills/tacas-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 tacas-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills tacas-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/TACAS-Skills/skills/tacas-submission .gemini/skills/tacas-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 "tacas-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-submission into .gemini/skills/tacas-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 tacas-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 tacas-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/TACAS-Skills/skills/tacas-submission .github/skills/tacas-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 "tacas-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-submission into .github/skills/tacas-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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 tacas-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 tacas-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/TACAS-Skills/skills/tacas-submission .opencode/skills/tacas-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 "tacas-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/TACAS-Skills/skills/tacas-submission into .opencode/skills/tacas-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tacas-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
tacas-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 680 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 TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool…
- Works in 5 steps: Confirm the category and its page limit;… → For a research paper, run the anonymity… → For a tool / tool-demo paper, stage the… → …
- Auditing a TACAS (ETAPS) submission for EasyChair readiness
- SKILL.md covers Step 0 — pick the category (it…, Format and page budget, The blind sweep — but only… and The mandatory-artifact reality…, plus 4 more sections
- Calls pdftotext
What it does
Tacas Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool, tool-demonstration), the correct LNCS page limit and llncs.cls format, the per-category blind mode (double-blind research vs single-blind tool/case-study), the mandatory tool-paper artifact deadline, and desk-reject triage before the firm ETAPS deadline.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. 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 TACAS (ETAPS) submission for EasyChair readiness
- Covering the choice among the four paper categories (research
- Tool-demonstration)
- The correct LNCS page limit and llncs.cls format
Example prompts
- “/tacas-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Confirm the category and its page limit; freeze the body early.
- For a research paper, run the anonymity sweep on the final PDF and any review artifact; for a
- For a tool / tool-demo paper, stage the mandatory artifact and its VM packaging on the
- Fill every EasyChair field — category, topics, co-authors, conflicts — a day early.
- 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
Tacas Submission loads about 1.5k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 680 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). 680 words, ~1,548 tokens.
Download SKILL.mdSave it as
.claude/skills/tacas-submission/SKILL.md (or your agent's skills folder).- name
- tacas-submission
- description
- Use when auditing a TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool, tool-demonstration), the correct LNCS page limit and llncs.cls format, the per-category blind mode (double-blind research vs single-blind tool/case-study), the mandatory tool-paper artifact deadline, and desk-reject triage before the firm ETAPS deadline.
TACAS Submission
Run this audit before uploading to the TACAS EasyChair site. TACAS is a main conference of
ETAPS, publishing in Springer LNCS (gold open access), and — unlike a single-track venue —
it has four paper categories whose rules differ in page limit, anonymity, and artifact
obligation. Every number below was read from the TACAS 2026 / ETAPS 2026 joint call on 2026-07-09
via search renderings of the etaps.org pages (see resources/official-source-map.md); treat them
as a one-cycle snapshot and reopen the live call first. ETAPS deadlines are advertised as firm
and not extended.
Step 0 — pick the category (it sets every other rule)
| Category | Page limit (llncs.cls) | Blind mode | Artifact |
|---|---|---|---|
| Regular research paper | ≤16 pages | Double-blind | Voluntary, post-acceptance |
| Case-study paper | ≤16 pages | Single-blind | Voluntary, post-acceptance |
| Regular tool paper | ≤16 pages | Single-blind | Mandatory, submitted after the paper, gates acceptance |
| Tool-demonstration paper | ≤6 pages | Single-blind | Mandatory, submitted after the paper, gates acceptance |
Page limits exclude the bibliography and a clearly marked appendix. Choosing the wrong category
is a substantive error, not a label: a research paper submitted as a tool paper will be held to a
tool paper's artifact bar, and vice versa. If unsure, run tacas-topic-selection first.
Format and page budget
- Springer LNCS
llncs.cls, unmodified. This is the LNCS path, not ACMacmartor IEEEIEEEtran— do not carry a template habit from a sibling venue. - Page limit for your category (16 or 6), counting all text and figures but not references or an end appendix. Material that does not fit may go in the appendix and/or a supplementary website, with access enabled and license clear.
- Margins, font, and spacing are fixed by
llncs.cls; recover space by editing, never by shrinking the template.
The blind sweep — but only where it applies
Anonymity at TACAS is per category. A regular research paper is double-blind; a case-study, regular tool, or tool-demonstration paper is single-blind and names its authors and tool.
For a regular research paper, run the mechanical anonymity pass:
# Research-paper (double-blind) anonymity check on the final PDF and any review artifact
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|acknowledg|grant|thanks' | head
grep -rniE 'our (tool|group|lab)|university of|@[a-z0-9.]+\.edu' artifact/ --include='*.md' | headOmit author names and institutions, cite your own prior work in the third person, drop identifying acknowledgements, and route any supplementary link through an anonymizing host. For a tool or case-study paper, do the opposite: name the tool clearly and make authorship and provenance unambiguous — anonymizing a single-blind tool paper is itself a mistake.
Show full SKILL.md (301 more words)Show less
The mandatory-artifact reality (tool and tool-demo papers)
For a regular tool or tool-demonstration paper the artifact is not optional and not
post-acceptance: it is submitted shortly after the paper (TACAS 2026: paper 16 Oct 2025,
mandatory artifact 30 Oct 2025), evaluated in parallel with the PC, and its outcome feeds the
acceptance decision. Plan the packaging before the paper deadline, not after. See
tacas-artifact-evaluation.
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Wrong category for the contribution | Held to the wrong bar | Re-scope to research / case-study / tool / tool-demo before submitting |
| Over the category page limit | Desk-reject-grade | Cut or move to appendix/website; references and appendix do not absorb body text |
llncs.cls altered (margins, font) | Format violation | Recompile clean, recover space editorially |
| Research paper not anonymized | Double-blind violation | Strip names, third-person self-cites, scrub PDF metadata, re-anonymize artifact |
| Tool/tool-demo paper with no artifact ready | Cannot meet the mandatory deadline | Build and stage the artifact now; it gates acceptance |
| Same work under review / published elsewhere | Dual-submission | Withdraw one venue; confirm the current concurrent-submission wording |
Final-week order of operations
- Confirm the category and its page limit; freeze the body early.
- For a research paper, run the anonymity sweep on the final PDF and any review artifact; for a tool/case-study paper, confirm the tool and authorship are clearly named.
- For a tool / tool-demo paper, stage the mandatory artifact and its VM packaging on the post-paper deadline.
- Fill every EasyChair field — category, topics, co-authors, conflicts — a day early.
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
Reverify each cycle
- Page limits per category and the current
llncs.clsrevision. - The per-category blind wording and which categories carry a mandatory artifact.
- Exact ETAPS dates, the abstract/full-paper gap, and dual-submission and AI-disclosure rules — all cycle-volatile.
Output format
[TACAS submission status] ready / blocked / needs work
[Category] research / case-study / regular tool / tool-demonstration
[Format] pages used (limit 16/6), llncs.cls compliance
[Blind mode] double-blind (research): clean / leaks: <where> | single-blind (other): named correctly? yes/no
[Artifact] mandatory (tool/tool-demo) staged? / voluntary (research/case-study) planned?
[Fix queue] <ordered, with owners and dates before the firm ETAPS 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 TACAS-Skills/skills/tacas-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Tacas 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 |
|---|---|---|---|---|---|---|
| Tacas Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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…
Related
Categories
Questions about Tacas Submission
What does Tacas Submission do?
A skill your agent uses when auditing a TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool…. Tacas Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills.cls format, the per-category blind mode (double-blind research vs single-blind tool/case-study), the mandatory tool-paper artifact deadline, and desk-reject triage before the firm ETAPS deadline.
When should I use Tacas Submission?
Tacas Submission fits situations like: auditing a TACAS (ETAPS) submission for EasyChair readiness; covering the choice among the four paper categories (research; tool-demonstration); the correct LNCS page limit and llncs.cls format.
How do I install Tacas Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-submission -a claude-code`. Or copy the skill folder (TACAS-Skills/skills/tacas-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/tacas-submission in your project. Claude Code loads it when a task matches its description.
How do I install Tacas Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-submission -a codex`. Or copy the skill folder (TACAS-Skills/skills/tacas-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/tacas-submission in your project. Codex loads it when a task matches its description.
Can I use Tacas 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 tacas-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/tacas-submission, .gemini/skills/tacas-submission, .github/skills/tacas-submission and .opencode/skills/tacas-submission in your project.
What does Tacas Submission need to run?
Going by SKILL.md and its folder, Tacas Submission needs the command-line tools its instructions call (pdftotext).
Does Tacas 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 Tacas 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 Tacas Submission use?
Tacas 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 Tacas Submission use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Tacas Submission?
Skills that share tags, products or a category with Tacas Submission: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tacas 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.