القائمة
Merge local paper changes back to the shared ~/.common-law/ global state. Use when the user asks to upstream changes, sync bib entries, or merge writing guide modifications. Presents a list of local modifications and lets the user select what to merge.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Compile a LaTeX academic paper with pdflatex. Use when the user asks to build, compile, or check the paper. Also run law-pagecount and law-verify after a successful build.
Run post-build verification checks on a compiled LaTeX paper. Checks for emdashes, undefined references and citations, mid-paragraph bold text, hyphens in prose, and missing appendix cross-references. Use after law-build succeeds.
Write experiment guides for handing off work from agent to human. Use when the user asks what experiments are needed, requests a task list for a student, or when todo.md contains items the agent cannot complete (code execution, data collection, figure generation, hardware access). Produce a concise guide with specific deliverables per experiment: CSV schema, plotting script, and final figure.
Parse reviewer feedback into a structured todo.md revision tracker for academic papers. Use when the user asks to triage reviews, extract actionable items from review comments, or create a revision plan from reviewer feedback. Flags uncertain items for human confirmation.
Create a new academic paper repository with the correct directory structure, venue template, and agent instruction files. Use when the user asks to create a new paper, bootstrap a paper project, start a new submission, or set up a paper repo for a specific venue (NSDI, SIGCOMM, APNet, arxiv).
Count pages per section in a compiled LaTeX paper PDF. Enables PDF bookmarks if disabled, then extracts section titles and page numbers from the PDF outline. Used by law-build after a successful compilation.
| name | law-upstream |
| description | Merge local paper changes back to the shared ~/.common-law/ global state. Use when the user asks to upstream changes, sync bib entries, or merge writing guide modifications. Presents a list of local modifications and lets the user select what to merge. |
Merge local paper modifications back to ~/.common-law/. This keeps the global bib file, writing guide, and build scripts in sync across all papers.
Three categories of local changes:
refs.bib that don't exist in ~/.common-law/bib/refs.bibbuild.sh, build.bat, or verify.shRun scripts/upstream-bib.sh to find new bib entries and scripts/upstream-claude.sh to find CLAUDE.md changes.
For script changes, diff the paper's scripts against the skill's canonical copies.
Show a grouped list:
Changes ready to upstream:
[Bib entries — 3 new]
1. extraref1 — "Machine Learning for Resource Management..." (Garcia, EuroSys 2025)
2. extraref2 — "Reinforcement Learning for Cluster Scheduling" (Nguyen, MLSys 2024)
3. extraref3 — "A Formal Analysis of Joint..." (Tanaka, PER 2025)
[CLAUDE.md changes]
4. Added "No hyphens" rule to Hard Prohibitions section
[Script changes]
(none)
Select items to upstream (e.g., "1,2,4" or "all"):
~/.common-law/bib/refs.bib, deduplicate by citation key~/.common-law/paper-style/CLAUDE.mdscripts/ directoryTell the user exactly what was merged and where.
After law-write or law-revise sessions that add citations, ask: "You added N new citations. Upstream them to the global bib?"
The user can say yes, no, or "later." Do not push.
scripts/upstream-bib.sh — finds new bib entries and handles deduplicationscripts/upstream-claude.sh — diffs CLAUDE.md and strips the narrative section