Paper Version Manager
Paste the following prompt into your AI chat to install this skill:
Please follow https://skillhub.cn/install/skillhub.md and install @user_8d26dabd/paper-version-manager.
About this skill
Problem Space
When a paper goes through multiple revisions, collaborator edits, and reviewer feedback, version history can become hard to audit: which section changed, why, whether a later draft is materially better, and if the author can safely roll back. Paper Version Manager treats paper version control as a lightweight engineering workflow rather than a pile of file snapshots.
How It Works and Limits
It focuses on four audit-oriented tasks:
- Lineage: maps inheritance, branching, and merge relationships across versions, including key milestones.
- Scoring: compares adjacent drafts on content completeness, logical completeness, closure, and AI-detection risk to surface regressions.
- Changelog: extracts P0–P3 changes from review reports into a structured CHANGELOG.
- Safe baseline: preserves a trusted baseline for rollback and integrity checks.
Use it for academic paper version governance, not as a generic git or cloud-storage replacement. Adjacent tasks such as review, submission, formatting, and citation cleanup should be routed to their own tools. The skill explicitly forbids deleting or altering version history to hide misconduct or fabricating edits to evade plagiarism detection; irreversible actions require human confirmation.
Use Cases
- After multiple revision rounds, record changes from V1.2 to V1.3, including revision points, decision rationale, and score deltas, then generate a structured CHANGELOG.
- After a peer-review report returns, extract P0-P3 issues from adjacent versions and use the four-dimension score to judge whether the current draft is closer to submittable.
- Before submission, verify that the final draft can be rolled back, preserve a safe baseline, and generate a version lineage tree for supervisor or collaborator review.
- When collaborator edits overwrite each other, audit the decision log to see who changed a section, why it changed, and whether the fix was implemented.
Best For
- Graduate students revising dissertations repeatedly, who need a rollback-safe baseline and a comparable version history.
- Journal paper authors responding to peer review, who need to confirm which P0 issues improved between versions.
- Research supervisors guiding multiple students, who need auditable version lineage and decision logs before final drafts.
- Academic compliance editors, who need to verify that version history is complete, traceable, and not fabricated to hide misconduct.
Related Skills
Creates themed learning sites by generating flashcards, lessons, quizzes, index, and progress pages into a deployable website.
End-to-end mathematical optimization modeling with Gurobi and Python, covering data validation, code generation, solving, result analysis, and iterative revision.
Executes an Eversheet Web CDP login using externally supplied baseUrl, username, and password, then verifies the page reaches a logged-in home state.
Clarify product goals, user flows, pages, data, and permissions, then output an implementation-ready development prompt and lightweight spec.