Agent skill · Code Review & Quality

hlr-revision-and-editing

Use when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page proofs to publication. Drives the edit cycle to completion; it does not manage the offer/expedite phase (hlr-placement-strategy) or the first editor handshake (hlr-student-editor-review).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-revision-and-editing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: Harvard-Law-Review-Skills/skills/hlr-revision-and-editing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Revision and Editing (hlr-revision-and-editing) After acceptance, an HLR piece goes through an **intensive, multi-round editing cycle** run by student editors — heavier and more iterative than at most journals. There is no single "R&R letter" as in peer review; instead there are successive passes (substantive, technical/line, Bluebook, proofs), each with deadlines. This skill keeps the cycle moving, protects the argument across rounds, and lands the piece in print without late surprises. ## When to trigger - The substantive edit is underway and rounds are stacking up - You receive markups, queries, or new source-pull requests between rounds - You disagree with a proposed change and must respond across a round - Page proofs arrive and need a careful final pass ## The edit cycle (round by round) | Round | Focus | Author's job | |-------|-------|--------------| | Substantive round(s) | Strengthen the argument; close gaps editors flagged | Revise on the merits; defend with reasons where warranted | | Technical / line round | Prose, clarity, house style | Approve or push back on specific edits, not en masse | | Bluebook / cite round | Every footnote conformed and verified | Supply pin

What's inside
Steps it walks through
  1. When to trigger
  2. The edit cycle (round by round)
  3. Working the cycle well
  4. Deadlines and momentum
  5. Checklist
  6. Anti-patterns
  7. Output format
  8. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the hlr-revision-and-editing skill do?

Use when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page proofs to publication. Drives the edit cycle to completion; it does not manage the offer/expedite phase (hlr-placement-strategy) or the first editor handshake (hlr-student-editor-review).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-revision-and-editing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going