resume-version-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

简历版本管理器

Resume Version Manager

以私有

resume-facts.yaml

为唯一事实源，为每次投递建立可回溯、可比较的母版和定制版本。HTML/PDF 是从已确认事实生成的交付物，不替代事实记录。

它不占用用户的主流程入口：在母版确认或 JD 定制版确认后记录版本即可；用户需要比较、恢复或维护投递记录时再展示版本操作。

Use the private

resume-facts.yaml

as the sole source of truth to create traceable, comparable master and customized versions for each application. HTML/PDF are deliverables generated from confirmed facts and do not replace fact records.

It does not occupy the user's main workflow entry: record the version only after the master version is confirmed or the JD customized version is confirmed; display version operations only when the user needs to compare, restore, or maintain application records.

先读

Preread

读取简历事实契约、JD 匹配报告模板和写作规范。

Read Resume Fact Contract, JD Matching Report Template and Writing Guidelines.

工作流

Workflow

找到或创建私有
```
resume-facts.yaml
```
和明确标识的母版；事实文件保存候选人全部已确认的 claim，不能被定制操作覆盖。
为一个公司/岗位/JD 创建独立目录：
```
tailored/<公司名>-<岗位>/
```
。
记录父版本、目标 JD、创建日期、使用的候选人事实、重排项、改写项、关键词来源、未匹配要求和待确认字段。
生成该版本的
```
resume_visual.html
```
，必要时生成
```
resume_ats.html
```
和
```
matching-analysis.md
```
；验证 PDF 页数、可提取文本和 HTML 溢出，并只记录 hash 对应当前文件的 valid manifest。
比较版本时按事实、顺序、措辞和样式分组；发现事实不一致时标记冲突并请求候选人确认。

Locate or create the private
```
resume-facts.yaml
```
and clearly identified master version; the fact file saves all confirmed claims of the candidate and cannot be overwritten by customization operations.
Create an independent directory for a company/position/JD:
```
tailored/<Company Name>-<Position>/
```
.
Record the parent version, target JD, creation date, candidate facts used, reordered items, rewritten items, keyword sources, unmatched requirements, and pending confirmation fields.
Generate the
```
resume_visual.html
```
for this version, generate
```
resume_ats.html
```
and
```
matching-analysis.md
```
if necessary; verify PDF page count, extractable text, and HTML overflow, and only record a valid manifest whose hash corresponds to the current file.
Group by facts, order, wording, and styles when comparing versions; mark conflicts and request candidate confirmation when fact inconsistencies are found.

Git 版本历史（推荐）

Git Version History (Recommended)

将

resume/

放在本地私有 Git 仓库中，用提交记录确认后的事实和投递版本；不要默认推送到公开远程仓库，简历可能包含联系方式和其他个人信息。

候选人确认母版变更后，创建一次说明明确的提交，例如：
```
更新母版：补充 RAG 项目
```
。
每次确认生成一份定制版后，创建一次提交，例如：
```
定制：字节跳动 - 前端实习生
```
。
比较、恢复或审计时，以提交差异为准；比较范围仍按事实、顺序、措辞和样式分组，并优先确认事实冲突。
只有候选人希望同时尝试互斥的母版方向时，才创建分支；普通的 JD 定制保存在
```
tailored/
```
目录并用提交追溯即可。
不自动执行 Git 初始化、提交、推送或覆盖；在每个会改变版本历史的操作前说明范围并取得候选人确认。

Place

resume/

in a local private Git repository, use commit records to confirm facts and application versions; do not push to public remote repositories by default, as resumes may contain contact information and other personal information.

After the candidate confirms changes to the master version, create a commit with a clear description, e.g.:
```
Update master version: Add RAG project
```
.
After confirming the generation of a customized version each time, create a commit, e.g.:
```
Customized: ByteDance - Frontend Intern
```
.
When comparing, restoring, or auditing, rely on commit differences; the comparison scope is still grouped by facts, order, wording, and styles, and fact conflicts are prioritized for confirmation.
Create branches only when the candidate wants to try mutually exclusive master version directions at the same time; ordinary JD customizations are saved in the
```
tailored/
```
directory and traced with commits.
Do not automatically perform Git initialization, commit, push, or overwrite; explain the scope and obtain the candidate's confirmation before each operation that changes the version history.

Recommended Directory Structure

text

resume/
├── resume.html                         # 母版
└── tailored/
    └── <公司名>-<岗位>/
        ├── resume_visual.html
        ├── resume_ats.html            # 按需生成
        ├── matching-analysis.md
        └── version-notes.md

version-notes.md

最少记录：父版本、所用

resume-facts.yaml

、JD 来源/日期、变更摘要、关键词来源、未匹配要求、待确认字段和导出验证结果。

若使用 Git，

version-notes.md

还应记录对应提交 ID，便于从定制版回到母版事实和生成依据。

text

resume/
├── resume.html                         # Master version
└── tailored/
    └── <Company Name>-<Position>/
        ├── resume_visual.html
        ├── resume_ats.html            # Generate on demand
        ├── matching-analysis.md
        └── version-notes.md

version-notes.md

should at least record: parent version,

resume-facts.yaml

used, JD source/date, change summary, keyword sources, unmatched requirements, pending confirmation fields, and export verification results.

If Git is used,

version-notes.md

should also record the corresponding commit ID to facilitate returning to the master version facts and generation basis from the customized version.

约束

Constraints

定制版只能重排、强调或改写已确认事实；回写母版需要用户明确要求。
命名可使用
```
姓名_岗位_公司_YYYYMM.pdf
```
，但以目标平台要求为准。
不通过删除历史版本、静默覆盖文件或伪造版本记录来“整理”工作区。

Customized versions can only reorder, emphasize, or rewrite confirmed facts; writing back to the master version requires explicit user request.
Naming can use
```
Name_Position_Company_YYYYMM.pdf
```
, but follow the requirements of the target platform.
Do not "organize" the workspace by deleting historical versions, silently overwriting files, or falsifying version records.