writing
Track manuscript draft revisions across sessions. Maintains an append-only journal (.writing-journal.md) backed by git history to compare planned edits against actual changes, surface trajectory drift, and keep research drafts aligned.
- License 许可
- MIT
- 最近更新
- 2026-10-29
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- writing
- license
- MIT
- version
- 0.2.0
- description
- Track manuscript draft revisions across sessions. Maintains an append-only journal (.writing-journal.md) backed by git history to compare planned edits against actual changes, surface trajectory drift, and keep research drafts aligned.
- allowed-tools
- [ "Read", "Write", "Edit", "Bash", "Grep", "Glob", "AskUserQuestion" ]
- disable-model-invocation
- true
02 资源文件 4
- 参考文档reference/journal-entry-template.md886 B
- 脚本scripts/append_entry.sh815 B
- 脚本scripts/gather_context.sh1.5 KB
- 脚本scripts/init_journal.sh1.2 KB
03 SKILL.md 正文
Writing
Persistent intent tracking for research manuscripts and proof drafts across multiple editing sessions.
This skill tracks forward intent via .writing-journal.md. At the start of every session, it inspects the journal and git diffs to generate a brief comparing where the draft was planned to go versus where recent edits actually went.
Comparison to other skills
academic-humanizerandresearch-paper-writing: Stateless single-pass prose editors. They refine clarity and tone for current text without tracking history across sessions. Usewritingto plan and track direction, then hand text toacademic-humanizerfor prose polishing.- Retrospective diff tools: Summarize past commits after they happen.
writingtracks future intent, checking git diffs against previously stated plans to catch unannounced changes in direction.
When to use
- Resuming work on an existing paper, proof, or grant draft with an active
.writing-journal.md. - Starting the first tracked session on a multi-session draft.
- Checking whether planned edits match earlier intentions before making changes.
When not to use
- Single-pass prose or grammar polish. Use
academic-humanizer. - Drafting a completely new outline from scratch with no prior history.
- Disposable one-off documents like emails or quick abstracts.
Journal storage: .writing-journal.md
- Location:
<draft-root>/.writing-journal.mddirectly alongside the manuscript. Keep it in git with the paper repository. - Format: Append-only markdown. Entries follow
reference/journal-entry-template.md:- ISO-8601 UTC timestamp heading.
- What changed: one sentence on substantive structural or technical edits (not a diff dump).
- Why: reason for the change.
- Stated direction: next planned steps, concrete enough to test in subsequent sessions.
- Do not edit historical entries. If correcting a past error, append a new entry explaining the correction.
- Drift detection outcomes:
- Aligned: Recent git changes match stated direction. Proceed to edits.
- Drifted: Git changes diverge from earlier direction. Alert the user before editing: note the discrepancy and ask whether this is an intentional pivot.
- No signal: Document is uncommitted or untouched in git since the last timestamp. Flag this as unverified drift risk.
Process
- Check for
<draft-root>/.writing-journal.md. If missing, runscripts/init_journal.sh <draft-root>and note that tracking begins now. - Gather history by running
scripts/gather_context.sh <manuscript-path> [n-commits]. Inspect the journal and git commit logs for the file. - Formulate the trajectory brief: Summarize previous planned steps, actual git diffs, and alignment status. Present this brief before making edits.
- If drifted, ask the user to clarify whether to adopt the new direction or return to the original plan.
- Apply the requested manuscript edits:
- For prose refinement, use
academic-humanizer. - For LaTeX compilation errors or bibliography format, use
latex. - For symbolic and algebraic proof verification, use
math.
- For prose refinement, use
- Record the session outcome by running
scripts/append_entry.sh <draft-root> "<what>" "<why>" "<direction>"with specific, testable next steps.
Scripts
Plain bash scripts located in scripts/:
init_journal.sh <draft-root>: Creates the journal file with header if absent.gather_context.sh <manuscript-path> [n-commits]: Outputs the journal content and recent git diffs.append_entry.sh <draft-root> <what> <why> <direction>: Appends an entry and fails if the journal file is missing.
04 同仓库更多 Skills
math
Enforces structured mathematical proof formatting (Claim, Assumptions, Proof, Where Used) and runs symbolic and numeric verification on extracted sub-claims using SymPy.
markitdown-converter
Convert documents (PDF, Word, Excel, PowerPoint, HTML, etc.) to markdown using Microsoft's markitdown library, then read the markdown output instead of binary files
latex
Focused LaTeX utility for compile-error log triage, bibliography validation, and venue template setup. Identifies precise error source files and lines from engine logs.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.