Agent skill · Code Review & Quality

hlr-student-editor-review

Use when working with Harvard Law Review (HLR) student editors after an offer — the intensive substantive and technical edit, the cite-check / source-pull, and author responsiveness. Manages the relationship and process; it does not run the pre-offer placement (hlr-placement-strategy) or the author-side cite apparatus build (hlr-footnotes-and-cite-check).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-student-editor-review --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-student-editor-review/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

# Student-Editor Review (hlr-student-editor-review) HLR is **student-edited**: once your piece is accepted, smart law students — not anonymous faculty peers — run an **intensive edit**. Expect substantive pushback on the argument, heavy technical editing, and a full **cite-check / source-pull** in which editors verify every footnote against the actual source. This is more hands-on than peer review at most journals. This skill helps you work *with* the editors and protect your argument while clearing the process. ## When to trigger - You have an offer and the editing process is beginning - Editors sent a marked-up draft, queries, or a source-pull request - You disagree with an edit and need to decide how to respond - A deadline for returning the edit or sources is approaching ## What the HLR edit involves | Stage | What editors do | What they need from you | |-------|-----------------|--------------------------| | Substantive edit | Press the argument, flag gaps, ask for clarification or support | Defend, clarify, or revise — engage on the merits | | Technical / line edit | Tighten prose, enforce house style and Bluebook | Approve or push back on specific changes | | **Cite-check /

What's inside
Steps it walks through
  1. When to trigger
  2. What the HLR edit involves
  3. The source-pull (the distinctive demand)
  4. Working with student editors (relationship craft)
  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-student-editor-review skill do?

Use when working with Harvard Law Review (HLR) student editors after an offer — the intensive substantive and technical edit, the cite-check / source-pull, and author responsiveness. Manages the relationship and process; it does not run the pre-offer placement (hlr-placement-strategy) or the author-side cite apparatus build (hlr-footnotes-and-cite-check).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-student-editor-review --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