CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
A skill your agent uses when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference…
Install Wsdm Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-workflow --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/WSDM-Skills/skills/wsdm-workflow .claude/skills/wsdm-workflow && 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 "wsdm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-workflow into .claude/skills/wsdm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-workflow", 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/WSDM-Skills/skills/wsdm-workflowType 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 wsdm-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-workflow --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/WSDM-Skills/skills/wsdm-workflow .agents/skills/wsdm-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wsdm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-workflow into .agents/skills/wsdm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-workflow", 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 wsdm-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-workflow --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/WSDM-Skills/skills/wsdm-workflow .cursor/skills/wsdm-workflow && 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 "wsdm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-workflow into .cursor/skills/wsdm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-workflow", 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 WSDM-Skills/skills/wsdm-workflow--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 wsdm-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wsdm-workflow --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/WSDM-Skills/skills/wsdm-workflow .gemini/skills/wsdm-workflow && 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 "wsdm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-workflow into .gemini/skills/wsdm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-workflow", 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 wsdm-workflowInstalls 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 wsdm-workflow -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/WSDM-Skills/skills/wsdm-workflow .github/skills/wsdm-workflow && 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 "wsdm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-workflow into .github/skills/wsdm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-workflow", 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 wsdm-workflow -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 wsdm-workflow --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/WSDM-Skills/skills/wsdm-workflow .opencode/skills/wsdm-workflow && 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 "wsdm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WSDM-Skills/skills/wsdm-workflow into .opencode/skills/wsdm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wsdm-workflow", 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
wsdm-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 744 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference…
- Works in 4 steps: One owner for the EasyChair record:… → The objection inventory (started at… → The artifact repo freezes at T-1w except… → …
- Backward milestone planning
- SKILL.md covers The annual clock, The September pressure valve, Alternate entrances to the… and Coordinating with the sibling…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wsdm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate entrances (demos, WSDM Cup, doctoral consortium), and coordination with sibling-venue deadlines.
Its SKILL.md is about 1.7k 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 Product & Project Management, covering Project management. 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
- Backward milestone planning
- The September short-paper fallback
- Alternate entrances (demos
- Doctoral consortium)
Example prompts
- “/wsdm-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- One owner for the EasyChair record: account, abstract text, author order,
- The objection inventory (started at T-8w) is a living document with named
- The artifact repo freezes at T-1w except README fixes - late code churn
- Log every date-fact with its source URL the day you verify it; August
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
No scripts in the folder and no shell commands in SKILL.md.
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
Wsdm Workflow loads about 1.7k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 744 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). 744 words, ~1,696 tokens.
Download SKILL.mdSave it as
.claude/skills/wsdm-workflow/SKILL.md (or your agent's skills folder).- name
- wsdm-workflow
- description
- Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate entrances (demos, WSDM Cup, doctoral consortium), and coordination with sibling-venue deadlines.
WSDM Workflow
Plan a WSDM campaign around the venue's defining rhythm: one deadline a year, in August, for a conference the following February - with no rebuttal stage between them. Missing August costs twelve months, and nothing after August can improve the outcome. Every date below is a 2026-cycle anchor (abstract 2025-08-07, paper 2025-08-14, notification 2025-10-23, conference 2026-02-22 to 26, Boise); the 2027 edition (20th, Hong Kong, February 15-19, 2027) had not published verified deadlines at this pack's check date - confirm them at wsdm-conference.org/2027 before committing the plan.
The annual clock
T-26w fit decision (wsdm-topic-selection) + evidence plan
T-20w datasets locked, split manifests written, baselines running
T-12w main results stable; ablation matrix complete
T-8w full draft; adversarial read #1 -> objection inventory
T-4w artifact repo review-ready; ethics section drafted
T-1w abstract registered (bidding-quality title+abstract)
Aug T=0 paper deadline, AoE <- everything ends here
Oct ~T+10w notification <- no interaction in between
Nov+ camera-ready + ACM production (dates from acceptance email)
Feb single-track conference (talk/poster, registration, travel)The unusual constraints, made explicit:
- Front-load quality. Venues with rebuttals let you defend a rushed evaluation; WSDM does not. The T-8w adversarial read is the highest-leverage meeting of the campaign - schedule it like a deadline.
- The August-to-October silence is planning time, not waiting time: prepare the camera-ready artifact conversion and, in parallel, the rejection fork (below), so either outcome executes immediately.
- February logistics are real work: winter travel, visas for the host country (Hong Kong in 2027), industry disclosure approvals for the final version - start each at notification, not in January.
The September pressure valve
Since 2026 the series runs a short-paper track with deadlines about a month after the long-paper deadline (2026 anchor: announced September 11/18, with registry evidence of an extension to September 18/25 - verify the current year's dates directly). Plan uses:
- A long paper that is honestly two results and a wish can be split in July: the strong, focused result targets the short track; the broader project waits a year and arrives with more evidence.
- A near-miss at the long deadline (evaluation incomplete) degrades gracefully to the short track instead of slipping twelve months.
- Do not treat "short" as "unfinished": the 2026 call asked for solid, empirically validated contributions, capped submissions at 10 per author, and desk-rejected placeholder abstracts.
Alternate entrances to the same room
| Entrance | Typical timing (verify per edition) | What it earns |
|---|---|---|
| Long paper | August deadline | Archival full paper + single-track talk |
| Short paper | ~September deadline (since 2026) | Archival concise paper |
| Demonstration | Autumn deadline; 4-page cap in 2026 | Archival demo paper + demo floor |
| WSDM Cup | Task-specific autumn schedule | Challenge standing + workshop-style exposure |
| Doctoral consortium | Autumn deadline | Mentoring + community entry for PhD students |
| Industry Day talk | CFP per edition (2026 theme: LLMs and agentic AI in industry) | Non-archival visibility with the practitioner half of the venue |
A lab shipping a system can rationally take two entrances in one year (e.g., short paper + demo) - check the current calls' dual-submission language first.
Show full SKILL.md (330 more words)Show less
Coordinating with the sibling calendar
WSDM's August deadline sits inside a lattice of neighbors (all timings approximate and cycle-volatile - verify each): SIGIR around January/February, TheWebConf around October, CIKM around May, RecSys in spring, KDD's two cycles around August and February. Two standard plays:
- Forward chain: a paper rejected from SIGIR (decisions in spring) has a natural summer revision window before WSDM's August deadline - the reviews arrive in time to act on them.
- Backward chain: a WSDM rejection in October reaches SIGIR or KDD Cycle 2 in winter with fixes applied. Map the chain before submitting, so the October decision triggers execution instead of deliberation.
Never dual-submit along the chain: these are archival venues with standard concurrent-submission prohibitions; the chain is sequential by definition.
Contingencies
- Deadline extension announced: treat extra days as validation time, not new-experiment time; late-added results are the least-reviewed and most-attacked parts of a paper at a no-rebuttal venue.
- A competing preprint appears in July: do not race it with rushed experiments. Add the contrast citation, sharpen the delta sentence, and let the August version be correct rather than first-and-fragile.
- Key experiment breaks at T-2w: invoke the valve - descope the claim to what stands, or pivot to the short track - rather than shipping a table you cannot defend to reviewers you cannot answer.
- Chair announcement contradicts the CFP: newest official instruction
wins; log both with dates (precedence order in
../../resources/external_tools.md).
Team operating rules
- One owner for the EasyChair record: account, abstract text, author order, conflicts, final PDF upload.
- The objection inventory (started at T-8w) is a living document with named owners per objection; unresolved rows at T-1w force claim reductions.
- The artifact repo freezes at T-1w except README fixes - late code churn breaks the numbers-match-paper invariant more often than it helps.
- Log every date-fact with its source URL the day you verify it; August deadline drift (extensions happen) is checked weekly in the final month against the official site, not social media.
Output format
[Cycle] target edition + verified deadlines (source + check date)
[Milestones] T-26w..T-0 with owners; current slack per milestone
[Valve decision] long / long+short split / short / defer, with reason
[Alternate entrances] pursued this year: <list or none>
[Chain map] pre-WSDM source venue / post-WSDM destination, with dates
[Logistics] visa / registration / disclosure lead items and start dates© 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 WSDM-Skills/skills/wsdm-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wsdm Workflow 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 |
|---|---|---|---|---|---|---|
| Wsdm Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.7k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Ichartjswanghetommy/ichartjs | 352 | — | ~4.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals in Hivemind via the hivemind CLI.
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 Wsdm Workflow
What does Wsdm Workflow do?
A skill your agent uses when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference…. Wsdm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate entrances (demos, WSDM Cup, doctoral consortium), and coordination with sibling-venue deadlines.
When should I use Wsdm Workflow?
Wsdm Workflow fits situations like: backward milestone planning; the September short-paper fallback; alternate entrances (demos; doctoral consortium).
How do I install Wsdm Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-workflow -a claude-code`. Or copy the skill folder (WSDM-Skills/skills/wsdm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wsdm-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Wsdm Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-workflow -a codex`. Or copy the skill folder (WSDM-Skills/skills/wsdm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wsdm-workflow in your project. Codex loads it when a task matches its description.
Can I use Wsdm Workflow 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 wsdm-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wsdm-workflow, .gemini/skills/wsdm-workflow, .github/skills/wsdm-workflow and .opencode/skills/wsdm-workflow in your project.
What does Wsdm Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Wsdm Workflow is instructions for the agent only.
Does Wsdm Workflow 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 Wsdm Workflow 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 Wsdm Workflow use?
Wsdm Workflow 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 Wsdm Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Wsdm Workflow?
Skills that share tags, products or a category with Wsdm Workflow: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.7k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wsdm Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.