菜单
Plain-language Git for a non-technical user — snapshots, backups, undo, and disaster recovery. Use for any Git operation beyond a routine commit, and whenever the user says save, back up, undo, or go back.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Build the manuscript to PDF/DOCX/HTML, create figures and diagrams, manage cross-references, and run writing-quality checks (lint, grammar, readability).
Search academic literature, manage the search queue, download papers, and verify sources. Use when the user wants to find papers, when working search-queue.md, or when adding references.
Pre-submission checks, bibliography verification, and peer-review responses. Use when the manuscript nears submission, when verifying references, or when responding to reviewers.
Create writing plans, section drafts, and manuscript prose. Use when drafting or editing any part of the paper, building evidence chains from notes, or planning the writing.
Conventions for projects that generate their own results — running models, labeling data, computing statistics. Use when writing or running experiment code, or when drafting sections that report original results.
Extract text from papers, summarize them, and create reading notes. Use when reading or summarizing a paper, and automatically after downloading one.
基于 SOC 职业分类
| name | git-for-beginners |
| description | Plain-language Git for a non-technical user — snapshots, backups, undo, and disaster recovery. Use for any Git operation beyond a routine commit, and whenever the user says save, back up, undo, or go back. |
The user thinks in "saving" and "backing up." Never make them learn Git. The forbidden-commands list lives in CLAUDE.md and always applies.
| Instead of... | Say... |
|---|---|
| "Let me commit your changes" | "Let me save a snapshot of your progress" |
| "I'll push to origin" | "I'll back up your work to GitHub" |
| "There are uncommitted changes" | "You have unsaved work — want me to save it?" |
| "Let me checkout that branch" | "Let me switch to a different version" |
| "There's a merge conflict" | "Two versions of the same section got edited differently — let me help you pick" |
| "I'll revert that commit" | "I'll undo those changes and save a new snapshot" |
| "Your working tree is dirty" | "You have some unsaved edits" |
git status && git diff # see what changed
git add manuscript/main.md notes/new-note.md # by name — never -A or .
git commit -m "Draft introduction and add 3 source papers"
Then: "I've saved a snapshot of your progress."
Offer to save after: drafting/editing a section, adding sources, creating notes, changing the outline or bibliography, before AND after any bulk operation, at session end, and before anything that touches many files.
git push → "Your work is backed up online. Even if something happens to your computer, everything is safe."
Never amend a pushed commit — it desyncs the user's backup.
git diff to see, then git checkout -- <specific file> — never git checkout .git log --oneline to find it, git show <hash>:<file> to view; recreate the old content as a new save rather than rewriting historygit status + git log --oneline -5. Almost everything is recoverable. Don't panic, don't run destructive commands to "fix" it