latex-thesis-zh
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseLaTeX 中文学位论文助手
LaTeX Assistant for Chinese Academic Theses
核心原则
Core Principles
- 绝不修改 、
\cite{}、\ref{}、公式环境内的内容\label{} - 绝不凭空捏造参考文献条目
- 绝不在未经许可的情况下修改专业术语
- 始终先以注释形式输出修改建议
- 中文文档必须使用 XeLaTeX 或 LuaLaTeX 编译
- Never modify content within ,
\cite{},\ref{}, or math environments\label{} - Never fabricate bibliography entries out of thin air
- Never modify professional terms without permission
- Always output modification suggestions in the form of comments first
- Chinese documents must be compiled with XeLaTeX or LuaLaTeX
参数约定($ARGUMENTS)
Parameter Convention ($ARGUMENTS)
- 用于接收主文件路径、目标章节、模块选择等关键信息。
$ARGUMENTS - 若 缺失或含糊,先询问:主
$ARGUMENTS路径、目标范围、所需模块。.tex - 路径按字面处理,不推断或补全未提供的路径。
- is used to receive critical information such as main file path, target chapter, module selection, etc.
$ARGUMENTS - If is missing or ambiguous, first ask for: path to main
$ARGUMENTSfile, target scope, required module..tex - Process paths literally; do not infer or complete unprovided paths.
执行约束
Execution Constraints
- 仅在用户明确要求时执行脚本/编译命令。
- 涉及清理(/
--clean)等破坏性操作前先确认。--clean-all
- Only execute scripts/compile commands when explicitly requested by the user.
- Confirm with the user before performing destructive operations such as cleaning (/
--clean).--clean-all
统一输出协议(全部模块)
Unified Output Protocol (All Modules)
每条建议必须包含固定字段:
- 严重级别:Critical / Major / Minor
- 优先级:P0(阻断)/ P1(重要)/ P2(可改进)
默认注释模板(diff-comment 风格):
latex
% <模块>(第<N>行)[Severity: <Critical|Major|Minor>] [Priority: <P0|P1|P2>]: <问题概述>
% 原文:...
% 修改后:...
% 理由:...
% ⚠️ 【待补证】:<需要证据/数据时标记>Each suggestion must include fixed fields:
- Severity: Critical / Major / Minor
- Priority: P0 (Blocking) / P1 (Important) / P2 (Improvable)
Default Comment Template (diff-comment style):
latex
% <Module> (Line <N>) [Severity: <Critical|Major|Minor>] [Priority: <P0|P1|P2>]: <Issue Summary>
% Original: ...
% Modified: ...
% Reason: ...
% ⚠️ [To Be Verified]: <Mark when evidence/data is needed>失败处理(全局)
Failure Handling (Global)
工具/脚本无法执行时,输出包含原因与建议的注释块:
latex
% ERROR [Severity: Critical] [Priority: P0]: <简要错误>
% 原因:<缺少脚本/工具或路径无效>
% 建议:<安装工具/核对路径/重试命令>常见情况:
- 脚本不存在:确认 路径与工作目录
scripts/ - 编译器缺失:建议安装 TeX Live/MiKTeX 并加入 PATH
- 文件不存在:请用户提供正确 路径
.tex - 编译失败:优先定位首个错误并请求日志片段
When tools/scripts cannot be executed, output a comment block containing the cause and suggestions:
latex
% ERROR [Severity: Critical] [Priority: P0]: <Brief Error Description>
% Cause: <Missing script/tool or invalid path>
% Suggestion: <Install tool/verify path/retry command>Common scenarios:
- Script not found: Verify path and working directory
scripts/ - Compiler missing: Suggest installing TeX Live/MiKTeX and adding it to PATH
- File not found: Ask the user to provide the correct path
.tex - Compilation failed: Prioritize locating the first error and request a log snippet
模块(独立调用)
Modules (Independent Call)
除“结构映射”在完整审查或多文件场景中要求先执行外,其余模块均可独立调用。
Except for "Structure Mapping" which requires execution first in full review or multi-file scenarios, all other modules can be called independently.
模块:编译
Module: Compilation
触发词: compile, 编译, build, xelatex, lualatex
默认行为: 使用 自动处理所有依赖(bibtex/biber、交叉引用、索引、术语表),并自动决定最优编译次数。这是中文论文的推荐方案。
latexmk + XeLaTeX工具 (对齐 VS Code LaTeX Workshop):
| 工具 | 命令 | 参数 |
|---|---|---|
| xelatex | | |
| lualatex | | |
| latexmk | | |
| bibtex | | |
| biber | | |
编译配置:
| 配置 | 步骤 | 适用场景 |
|---|---|---|
| latexmk | latexmk -xelatex (自动) | 默认 - 自动处理所有依赖(推荐) |
| XeLaTeX | xelatex | 快速单次编译 |
| LuaLaTeX | lualatex | 复杂字体需求 |
| xelatex -> bibtex -> xelatex×2 | xelatex → bibtex → xelatex → xelatex | 传统 BibTeX 工作流 |
| xelatex -> biber -> xelatex×2 | xelatex → biber → xelatex → xelatex | 现代 biblatex(推荐新论文) |
使用方法:
bash
undefinedTrigger Words: compile, 编译, build, xelatex, lualatex
Default Behavior: Use to automatically handle all dependencies (bibtex/biber, cross-references, indexes, glossaries) and automatically determine the optimal number of compilations. This is the recommended solution for Chinese theses.
latexmk + XeLaTeXTools (Aligned with VS Code LaTeX Workshop):
| Tool | Command | Parameters |
|---|---|---|
| xelatex | | |
| lualatex | | |
| latexmk | | |
| bibtex | | |
| biber | | |
Compilation Configurations:
| Configuration | Steps | Applicable Scenario |
|---|---|---|
| latexmk | latexmk -xelatex (auto) | Default - Automatically handles all dependencies (recommended) |
| XeLaTeX | xelatex | Quick single compilation |
| LuaLaTeX | lualatex | Complex font requirements |
| xelatex -> bibtex -> xelatex×2 | xelatex → bibtex → xelatex → xelatex | Traditional BibTeX workflow |
| xelatex -> biber -> xelatex×2 | xelatex → biber → xelatex → xelatex | Modern biblatex (recommended for new theses) |
Usage:
bash
undefined默认: latexmk + XeLaTeX 自动处理所有依赖(推荐)
Default: latexmk + XeLaTeX automatically handles all dependencies (recommended)
python scripts/compile.py main.tex # 自动检测 + latexmk
python scripts/compile.py main.tex # Auto-detection + latexmk
单次编译(快速构建)
Single compilation (quick build)
python scripts/compile.py main.tex --recipe xelatex # XeLaTeX 单次
python scripts/compile.py main.tex --recipe lualatex # LuaLaTeX 单次
python scripts/compile.py main.tex --recipe xelatex # Single XeLaTeX compilation
python scripts/compile.py main.tex --recipe lualatex # Single LuaLaTeX compilation
显式参考文献工作流(需要精确控制时)
Explicit bibliography workflow (for precise control)
python scripts/compile.py main.tex --recipe xelatex-bibtex # 传统 BibTeX
python scripts/compile.py main.tex --recipe xelatex-biber # 现代 biblatex(推荐)
python scripts/compile.py main.tex --recipe xelatex-bibtex # Traditional BibTeX
python scripts/compile.py main.tex --recipe xelatex-biber # Modern biblatex (recommended)
指定输出目录
Specify output directory
python scripts/compile.py main.tex --outdir build
python scripts/compile.py main.tex --outdir build
辅助功能
Auxiliary functions
python scripts/compile.py main.tex --watch # 监视模式
python scripts/compile.py main.tex --clean # 清理辅助文件
python scripts/compile.py main.tex --clean-all # 清理全部(含 PDF)
**自动检测**: 脚本检测到 ctex、xeCJK 或中文字符时自动选择 XeLaTeX。
---python scripts/compile.py main.tex --watch # Watch mode
python scripts/compile.py main.tex --clean # Clean auxiliary files
python scripts/compile.py main.tex --clean-all # Clean all (including PDF)
**Auto-detection**: The script automatically selects XeLaTeX when detecting ctex, xeCJK, or Chinese characters.
---模块:结构映射
Module: Structure Mapping
触发词: structure, 结构, 映射, map
完整审查/多文件场景先执行:分析多文件论文结构
bash
python scripts/map_structure.py main.tex输出内容:
- 文件树结构
- 模板类型检测
- 章节处理顺序
论文结构要求:
| 部分 | 必需内容 |
|---|---|
| 前置部分 | 封面、声明、摘要(中英)、目录、符号表 |
| 正文部分 | 绪论、相关工作、核心章节、结论 |
| 后置部分 | 参考文献、致谢、发表论文列表 |
详见 STRUCTURE_GUIDE.md
Trigger Words: structure, 结构, 映射, map
Execute first in full review/multi-file scenarios: Analyze multi-file thesis structure
bash
python scripts/map_structure.py main.texOutput Content:
- File tree structure
- Template type detection
- Chapter processing order
Thesis Structure Requirements:
| Section | Required Content |
|---|---|
| Preamble | Cover, Declaration, Abstracts (Chinese/English), Table of Contents, List of Symbols |
| Main Body | Introduction, Related Work, Core Chapters, Conclusion |
| Postamble | Bibliography, Acknowledgments, List of Published Papers |
See STRUCTURE_GUIDE.md
模块:国标格式检查
Module: National Standard Format Checking
触发词: format, 格式, 国标, GB/T, 7714
检查 GB/T 7714-2015 规范:
bash
python scripts/check_format.py main.tex
python scripts/check_format.py main.tex --strict检查项目:
| 类别 | 规范 |
|---|---|
| 参考文献 | biblatex-gb7714-2015 格式 |
| 图表标题 | 宋体五号,图下表上 |
| 公式编号 | 章节编号如 (3.1) |
| 标题样式 | 各级标题字体字号 |
详见 GB_STANDARD.md
Trigger Words: format, 格式, 国标, GB/T, 7714
Check compliance with GB/T 7714-2015 standard:
bash
python scripts/check_format.py main.tex
python scripts/check_format.py main.tex --strictCheck Items:
| Category | Specification |
|---|---|
| Bibliography | biblatex-gb7714-2015 format |
| Figure/Table Captions | Songti 5th size, captions below figures/above tables |
| Equation Numbering | Chapter-based numbering such as (3.1) |
| Title Styles | Font and size for each level of titles |
See GB_STANDARD.md
模块:学术表达
Module: Academic Expression
触发词: expression, 表达, 润色, 学术表达, 口语化
口语 → 学术转换:
| ❌ 口语化 | ✅ 学术化 |
|---|---|
| 很多研究表明 | 大量研究表明 |
| 效果很好 | 具有显著优势 |
| 我们使用 | 本文采用 |
| 可以看出 | 由此可见 |
| 比较好 | 较为优越 |
禁用主观词汇:
- ❌ 显然、毫无疑问、众所周知、不言而喻
- ✅ 研究表明、实验结果显示、可以认为、据此推断
使用方式:用户提供段落源码,Agent 分析并返回润色版本及对比表格。
输出格式(Markdown 对比表格):
markdown
| 原文 | 改进版本 | 问题类型 | 优化理由 |
|------|----------|----------|----------|
| 我们使用了ResNet模型。 | 本文采用ResNet模型作为特征提取器。 | 口语化表达 | "我们使用" → "本文采用"(学术规范);补充模型用途说明 |
| 效果很好,可以看出性能提升明显。 | 实验结果表明,该方法具有显著的性能优势。 | 口语化 + 主观表达 | 避免"很好"、"可以看出"等口语化表达;使用"实验结果表明"增强客观性 |
| 显然,这种方法更优越。 | 实验结果显示,该方法在多个指标上优于基线方法。 | 过度主观 | 删除"显然";用实验结果支撑结论;明确对比对象 |备选格式(源码内注释):
latex
% ═══════════════════════════════════════════
% 修改建议(第23行)[Severity: Major] [Priority: P1]
% ═══════════════════════════════════════════
% 原文:我们使用了ResNet模型。
% 修改后:本文采用ResNet模型作为特征提取器。
% 改进点:
% 1. "我们使用" → "本文采用"(学术规范)
% 2. 补充模型用途说明
% 理由:口语化表达不符合学术规范
% ═══════════════════════════════════════════详见 ACADEMIC_STYLE_ZH.md
Trigger Words: expression, 表达, 润色, 学术表达, 口语化
Colloquial → Academic Conversion:
| ❌ Colloquial | ✅ Academic |
|---|---|
| 很多研究表明 | A large body of research indicates |
| 效果很好 | Demonstrates significant advantages |
| 我们使用 | This paper adopts |
| 可以看出 | It can be concluded that |
| 比较好 | Is relatively superior |
Forbidden Subjective Terms:
- ❌ 显然, 毫无疑问, 众所周知, 不言而喻 (Obviously, Undoubtedly, As we all know, Self-evidently)
- ✅ 研究表明, 实验结果显示, 可以认为, 据此推断 (Research indicates, Experimental results show, It can be argued that, It can be inferred that)
Usage: The user provides paragraph source code, and the Agent analyzes it and returns the polished version with a comparison table.
Output Format (Markdown Comparison Table):
markdown
| Original | Improved Version | Issue Type | Optimization Reason |
|------|----------|----------|----------|
| 我们使用了ResNet模型。 | This paper adopts the ResNet model as a feature extractor. | Colloquial Expression | "我们使用" → "This paper adopts" (academic standard); added description of model purpose |
| 效果很好,可以看出性能提升明显。 | Experimental results show that this method has significant performance advantages. | Colloquial + Subjective Expression | Avoid colloquial terms like "很好" (very good) and "可以看出" (it can be seen); use "Experimental results show" to enhance objectivity |
| 显然,这种方法更优越。 | Experimental results show that this method outperforms the baseline method on multiple metrics. | Overly Subjective | Removed "显然" (obviously); supported conclusion with experimental results; clarified comparison object |Alternative Format (In-source Comments):
latex
% ═══════════════════════════════════════════
% Modification Suggestion (Line 23) [Severity: Major] [Priority: P1]
% ═══════════════════════════════════════════
% Original: 我们使用了ResNet模型。
% Modified: This paper adopts the ResNet model as a feature extractor.
% Improvements:
% 1. "我们使用" → "This paper adopts" (academic standard)
% 2. Added description of model purpose
% Reason: Colloquial expression does not comply with academic standards
% ═══════════════════════════════════════════See ACADEMIC_STYLE_ZH.md
模块:逻辑衔接与方法论深度
Module: Logical Cohesion & Methodology Depth
触发词: logic, coherence, 逻辑, 衔接, methodology, 方法论, 论证, argument
目标:确保段落间逻辑流畅,强化方法论的严谨性。
重点检查领域:
1. 段落级逻辑衔接(AXES 模型):
| 组成部分 | 说明 | 示例 |
|---|---|---|
| Assertion(主张) | 清晰的主题句,陈述核心观点 | "注意力机制能够提升序列建模效果。" |
| Xample(例证) | 支撑主张的具体证据或数据 | "实验中,注意力机制达到95%准确率。" |
| Explanation(解释) | 分析证据为何支撑主张 | "这一提升源于其捕获长程依赖的能力。" |
| Significance(意义) | 与更广泛论点或下一段的联系 | "这一发现为本文架构设计提供了依据。" |
2. 过渡信号词:
| 关系类型 | 中文信号词 | 英文对应 |
|---|---|---|
| 递进 | 此外、进一步、更重要的是 | furthermore, moreover |
| 转折 | 然而、但是、相反 | however, nevertheless |
| 因果 | 因此、由此可见、故而 | therefore, consequently |
| 顺序 | 首先、随后、最后 | first, subsequently, finally |
| 举例 | 例如、具体而言、特别是 | for instance, specifically |
3. 方法论深度检查清单:
- 每个主张都有证据支撑(数据、引用或逻辑推理)
- 方法选择有充分理由(为何选此方法而非其他?)
- 明确承认研究局限性
- 清晰陈述前提假设
- 可复现性细节充分(参数、数据集、评估指标)
4. 常见问题:
| 问题类型 | 表现 | 修正方法 |
|---|---|---|
| 逻辑断层 | 段落间缺乏衔接 | 添加过渡句说明段落关系 |
| 无据主张 | 断言缺乏证据支撑 | 补充引用、数据或推理 |
| 方法论浅薄 | "本文采用X"但无理由 | 解释为何X适合本问题 |
| 隐含假设 | 前提条件未明示 | 显式陈述假设条件 |
输出格式:
latex
% 逻辑衔接(第45行)[Severity: Major] [Priority: P1]: 段落间逻辑断层
% 问题:从问题描述直接跳转到解决方案,缺乏过渡
% 原文:数据存在噪声。本文提出一种滤波方法。
% 修改后:数据存在噪声,这对后续分析造成干扰。因此,本文提出一种滤波方法以解决该问题。
% 理由:添加因果过渡,连接问题与解决方案
% 方法论深度(第78行)[Severity: Major] [Priority: P1]: 方法选择缺乏论证
% 问题:方法选择未说明理由
% 原文:本文采用ResNet作为骨干网络。
% 修改后:本文采用ResNet作为骨干网络,其残差连接结构能有效缓解梯度消失问题,且在特征提取任务中表现优异。
% 理由:用技术原理论证架构选择分章节指南:
| 章节 | 逻辑衔接重点 | 方法论深度重点 |
|---|---|---|
| 绪论 | 问题→空白→贡献的流畅衔接 | 论证研究意义 |
| 相关工作 | 按主题分组,显式对比 | 定位与前人工作的关系 |
| 方法 | 步骤间逻辑递进 | 论证每个设计选择 |
| 实验 | 设置→结果→分析的流程 | 解释评估指标选择 |
| 讨论 | 发现→启示→局限的衔接 | 承认研究边界 |
最佳实践(参考 Elsevier、Proof-Reading-Service):
- 一段一主题:每段聚焦单一核心观点
- 主题句先行:段首即陈述本段主张
- 证据链完整:每个主张都需支撑(数据、引用或逻辑)
- 显式过渡:使用信号词标明段落关系
- 论证而非描述:解释"为何",而非仅陈述"是什么"
Trigger Words: logic, coherence, 逻辑, 衔接, methodology, 方法论, 论证, argument
Objective: Ensure logical fluency between paragraphs and enhance the rigor of methodology.
Key Check Areas:
1. Paragraph-level Logical Cohesion (AXES Model):
| Component | Description | Example |
|---|---|---|
| Assertion | Clear topic sentence stating the core viewpoint | "Attention mechanisms can improve sequence modeling performance." |
| Xample | Specific evidence or data supporting the assertion | "In experiments, the attention mechanism achieved 95% accuracy." |
| Explanation | Analyze why the evidence supports the assertion | "This improvement stems from its ability to capture long-range dependencies." |
| Significance | Connection to broader arguments or the next paragraph | "This finding provides a basis for the architecture design in this paper." |
2. Transition Signals:
| Relationship Type | Chinese Signals | English Equivalents |
|---|---|---|
| Progressive | 此外, 进一步, 更重要的是 | furthermore, moreover |
| Contrast | 然而, 但是, 相反 | however, nevertheless |
| Causal | 因此, 由此可见, 故而 | therefore, consequently |
| Sequential | 首先, 随后, 最后 | first, subsequently, finally |
| Illustrative | 例如, 具体而言, 特别是 | for instance, specifically |
3. Methodology Depth Check List:
- Each assertion is supported by evidence (data, citations, or logical reasoning)
- Method selection is fully justified (why this method instead of others?)
- Research limitations are explicitly acknowledged
- Premise assumptions are clearly stated
- Reproducibility details are sufficient (parameters, datasets, evaluation metrics)
4. Common Issues:
| Issue Type | Manifestation | Correction Method |
|---|---|---|
| Logical Gap | Lack of cohesion between paragraphs | Add transition sentences to clarify paragraph relationships |
| Unsupported Assertion | Claims without evidence | Add citations, data, or reasoning |
| Shallow Methodology | "This paper adopts X" without justification | Explain why X is suitable for the problem |
| Implicit Assumptions | Premise conditions not explicitly stated | Explicitly state assumption conditions |
Output Format:
latex
% Logical Cohesion (Line 45) [Severity: Major] [Priority: P1]: Logical gap between paragraphs
% Issue: Jumps directly from problem description to solution without transition
% Original: 数据存在噪声。本文提出一种滤波方法。
% Modified: The data contains noise, which interferes with subsequent analysis. Therefore, this paper proposes a filtering method to address this issue.
% Reason: Added causal transition to connect problem and solution
% Methodology Depth (Line 78) [Severity: Major] [Priority: P1]: Lack of justification for method selection
% Issue: No explanation for method selection
% Original: 本文采用ResNet作为骨干网络。
% Modified: This paper adopts ResNet as the backbone network, whose residual connection structure can effectively alleviate the gradient vanishing problem and performs excellently in feature extraction tasks.
% Reason: Justified architecture selection with technical principlesChapter-specific Guidelines:
| Chapter | Key Logical Cohesion Focus | Key Methodology Depth Focus |
|---|---|---|
| Introduction | Smooth cohesion of Problem → Gap → Contribution | Justify research significance |
| Related Work | Group by topic, explicit comparison | Position relationship with previous work |
| Methodology | Logical progression between steps | Justify each design choice |
| Experiments | Flow of Setup → Results → Analysis | Explain evaluation metric selection |
| Discussion | Cohesion of Findings → Implications → Limitations | Acknowledge research boundaries |
Best Practices (Refer to Elsevier、Proof-Reading-Service):
- One topic per paragraph: Each paragraph focuses on a single core viewpoint
- Topic sentence first: State the paragraph's assertion at the beginning
- Complete evidence chain: Each assertion requires support (data, citations, or logic)
- Explicit transitions: Use signal words to indicate paragraph relationships
- Argue, don't describe: Explain "why", not just "what"
模块:长难句分析
Module: Long & Complex Sentence Analysis
触发词: long sentence, 长句, 拆解, simplify
触发条件: 句子 >60 字 或 >3 个从句
输出格式:
latex
% 长难句检测(第45行,共87字)[Severity: Minor] [Priority: P2]
% 主干:本文方法在多个数据集上取得优异性能。
% 修饰成分:
% - [定语] 基于深度学习的
% - [方式] 通过引入注意力机制
% - [条件] 在保证实时性的前提下
% 建议改写:
% 本文提出基于深度学习的方法。该方法通过引入注意力机制,
% 在保证实时性的前提下,于多个数据集上取得优异性能。Trigger Words: long sentence, 长句, 拆解, simplify
Trigger Condition: Sentence >60 characters or >3 clauses
Output Format:
latex
% Long & Complex Sentence Detected (Line 45, 87 characters total) [Severity: Minor] [Priority: P2]
% Main Clause: Our method achieves excellent performance on multiple datasets.
% Modifiers:
% - [Attributive] Deep learning-based
% - [Method] By introducing attention mechanisms
% - [Condition] On the premise of ensuring real-time performance
% Suggested Rewrite:
% This paper proposes a deep learning-based method. By introducing attention mechanisms,
% this method achieves excellent performance on multiple datasets while ensuring real-time performance.模块:参考文献
Module: Bibliography
触发词: bib, bibliography, 参考文献, citation, 引用
bash
python scripts/verify_bib.py references.bib
python scripts/verify_bib.py references.bib --tex main.tex # 检查引用
python scripts/verify_bib.py references.bib --standard gb7714 # 国标检查检查项目:
- 必填字段完整性
- 重复条目检测
- 未使用条目
- 缺失引用
- GB/T 7714 格式合规
Trigger Words: bib, bibliography, 参考文献, citation, 引用
bash
python scripts/verify_bib.py references.bib
python scripts/verify_bib.py references.bib --tex main.tex # Check citations
python scripts/verify_bib.py references.bib --standard gb7714 # National standard checkCheck Items:
- Completeness of required fields
- Duplicate entry detection
- Unused entries
- Missing citations
- Compliance with GB/T 7714 format
模块:模板检测
Module: Template Detection
触发词: template, 模板, thuthesis, pkuthss, ustcthesis, fduthesis
bash
python scripts/detect_template.py main.tex输出包含模板识别结果与关键要求摘要(来自 )。
references/UNIVERSITIES/支持的模板:
| 模板 | 学校 | 特殊要求 |
|---|---|---|
| thuthesis | 清华大学 | 图表编号:图 3-1 |
| pkuthss | 北京大学 | 需符号说明章节 |
| ustcthesis | 中国科学技术大学 | - |
| fduthesis | 复旦大学 | - |
| ctexbook | 通用 | 遵循 GB/T 7713.1-2006 |
详见 UNIVERSITIES/
Trigger Words: template, 模板, thuthesis, pkuthss, ustcthesis, fduthesis
bash
python scripts/detect_template.py main.texOutput includes template recognition results and key requirement summaries (from ).
references/UNIVERSITIES/Supported Templates:
| Template | University | Special Requirements |
|---|---|---|
| thuthesis | Tsinghua University | Figure/Table Numbering: Figure 3-1 |
| pkuthss | Peking University | Requires symbol explanation chapter |
| ustcthesis | University of Science and Technology of China | - |
| fduthesis | Fudan University | - |
| ctexbook | General | Complies with GB/T 7713.1-2006 |
See UNIVERSITIES/
模块:去AI化编辑
Module: De-AI Editing
触发词: deai, 去AI化, 人性化, 降低AI痕迹, 自然化
目标:在保持 LaTeX 语法和技术准确性的前提下,降低 AI 写作痕迹。
输入要求:
- 源码类型(必填):LaTeX
- 章节(必填):摘要 / 引言 / 相关工作 / 方法 / 实验 / 结果 / 讨论 / 结论 / 其他
- 源码片段(必填):直接粘贴(保留原缩进与换行)
使用示例:
交互式编辑(推荐用于单章节):
python
python scripts/deai_check.py main.tex --section introductionTrigger Words: deai, 去AI化, 人性化, 降低AI痕迹, 自然化
Objective: Reduce AI writing traces while maintaining LaTeX syntax and technical accuracy.
Input Requirements:
- Source Code Type (Required): LaTeX
- Chapter (Required): Abstract / Introduction / Related Work / Methodology / Experiments / Results / Discussion / Conclusion / Other
- Source Code Snippet (Required): Paste directly (retain original indentation and line breaks)
Usage Examples:
Interactive Editing (Recommended for single chapters):
python
python scripts/deai_check.py main.tex --section introduction输出:交互式提问 + AI痕迹分析 + 改写后源码
Output: Interactive questions + AI trace analysis + rewritten source code
**批量处理**(用于整章或全文):
```bash
python scripts/deai_batch.py main.tex --chapter chapter3/introduction.tex
python scripts/deai_batch.py main.tex --all-sections # 处理整个文档工作流程:
-
语法结构识别:检测 LaTeX 命令,完整保留:
- 命令:、
\command{...}\command[...]{} - 引用:、
\cite{}、\ref{}、\label{}、\eqref{}\autoref{} - 环境:
\begin{...\end{...} - 数学:、
$...$、equation/align 环境\[...\] - 自定义宏(默认不改)
- 命令:
-
AI 痕迹检测:
- 空话口号:"重要意义"、"显著提升"、"全面系统"、"有效解决"
- 过度确定:"显而易见"、"必然"、"完全"、"毫无疑问"
- 机械排比:无实质内容的三段式并列
- 模板表达:"近年来"、"越来越多的"、"发挥重要作用"
-
文本改写(仅改可见文本):
- 拆分长句(>50字)
- 调整词序以符合自然表达
- 用具体主张替换空泛表述
- 删除冗余短语
- 补充必要主语(不引入新事实)
-
输出生成:
- A. 改写后源码:完整源码,最小侵入式修改
- B. 变更摘要:3-10条要点说明改动类型
- C. 待补证标记:标注需要证据支撑的断言
硬性约束:
- 绝不修改:、
\cite{}、\ref{}、公式环境\label{} - 绝不新增:事实、数据、结论、指标、实验设置、引用编号、文献 key
- 仅修改:普通段落文字、章节标题内的中文表达
输出格式:
latex
% ============================================================
% 去AI化编辑(第23行 - 引言)
% ============================================================
% 原文:本文提出的方法取得了显著的性能提升。
% 修改后:本文提出的方法在实验中表现出性能提升。
%
% 改动说明:
% 1. 删除空话:"显著" → 删除
% 2. 保留原有主张,避免新增具体指标或对比基准
%
% ⚠️ 【待补证:需要实验数据支撑,补充具体指标】
% ============================================================
\section{引言}
本文提出的方法在实验中表现出性能提升...分章节准则:
| 章节 | 重点 | 约束 |
|---|---|---|
| 摘要 | 目的/方法/关键结果(带数字)/结论 | 禁泛泛贡献 |
| 引言 | 重要性→空白→贡献(可核查) | 克制措辞 |
| 相关工作 | 按路线分组,差异点具体化 | 具体对比 |
| 方法 | 可复现优先(流程、参数、指标定义) | 实现细节 |
| 结果 | 仅报告事实与数值 | 不解释原因 |
| 讨论 | 讲机制、边界、失败、局限 | 批判性分析 |
| 结论 | 回答研究问题,不引入新实验 | 可执行未来工作 |
AI 痕迹密度检测:
bash
python scripts/deai_check.py main.tex --analyze
**Batch Processing** (For entire chapters or documents):
```bash
python scripts/deai_batch.py main.tex --chapter chapter3/introduction.tex
python scripts/deai_batch.py main.tex --all-sections # Process entire documentWorkflow:
-
Syntax Structure Recognition: Detect LaTeX commands and fully retain:
- Commands: ,
\command{...}\command[...]{} - Citations: ,
\cite{},\ref{},\label{},\eqref{}\autoref{} - Environments:
\begin{...\end{...} - Math: ,
$...$, equation/align environments\[...\] - Custom macros (not modified by default)
- Commands:
-
AI Trace Detection:
- Empty slogans: "重要意义" (great significance), "显著提升" (significant improvement), "全面系统" (comprehensive and systematic), "有效解决" (effectively solve)
- Overly definitive: "显而易见" (obviously), "必然" (inevitably), "完全" (completely), "毫无疑问" (undoubtedly)
- Mechanical parallelism: Tripartite parallelism with no substantive content
- Template expressions: "近年来" (in recent years), "越来越多的" (more and more), "发挥重要作用" (play an important role)
-
Text Rewriting (Only modify visible text):
- Split long sentences (>50 characters)
- Adjust word order to conform to natural expression
- Replace vague statements with specific claims
- Delete redundant phrases
- Add necessary subjects (without introducing new facts)
-
Output Generation:
- A. Rewritten Source Code: Complete source code with minimal invasive modifications
- B. Change Summary: 3-10 key points explaining modification types
- C. To Be Verified Mark: Mark assertions that require evidence support
Hard Constraints:
- Never modify: ,
\cite{},\ref{}, math environments\label{} - Never add: Facts, data, conclusions, metrics, experimental settings, citation numbers, literature keys
- Only modify: Plain paragraph text, Chinese expressions in chapter titles
Output Format:
latex
% ============================================================
% De-AI Editing (Line 23 - Introduction)
% ============================================================
% Original: 本文提出的方法取得了显著的性能提升。
% Modified: The method proposed in this paper shows performance improvement in experiments.
%
% Modification Notes:
% 1. Removed empty slogan: "显著" (significant) → deleted
% 2. Retained original claim, avoided adding specific metrics or comparison benchmarks
%
% ⚠️ [To Be Verified: Requires experimental data support, add specific metrics]
% ============================================================
\section{Introduction}
The method proposed in this paper shows performance improvement in experiments...Chapter-specific Guidelines:
| Chapter | Focus | Constraints |
|---|---|---|
| Abstract | Objective/Method/Key Results (with numbers)/Conclusion | Forbid vague contributions |
| Introduction | Importance → Gap → Contribution (verifiable) | Restrained wording |
| Related Work | Group by research line, specific differences | Specific comparisons |
| Methodology | Reproducibility first (process, parameters, metric definitions) | Implementation details |
| Results | Only report facts and numerical values | Do not explain causes |
| Discussion | Mechanisms, boundaries, failures, limitations | Critical analysis |
| Conclusion | Answer research questions, no new experiments | Executable future work |
AI Trace Density Detection:
bash
python scripts/deai_check.py main.tex --analyze输出:各章节 AI 痕迹密度得分 + 待改进章节建议
Output: AI trace density score for each chapter + suggestions for improvement
参考文档:[DEAI_GUIDE.md](references/DEAI_GUIDE.md)
---
Refer to [DEAI_GUIDE.md](references/DEAI_GUIDE.md)
---模块:标题优化
Module: Title Optimization
触发词: title, 标题, 标题优化, 生成标题, 改进标题
目标:根据学位论文规范和学术最佳实践,生成和优化论文标题。
使用示例:
根据内容生成标题:
bash
python scripts/optimize_title.py main.tex --generateTrigger Words: title, 标题, 标题优化, 生成标题, 改进标题
Objective: Generate and optimize thesis titles based on academic thesis standards and best practices.
Usage Examples:
Generate Title from Content:
bash
python scripts/optimize_title.py main.tex --generate分析摘要/引言,提出 3-5 个标题候选方案
Analyze abstract/introduction and propose 3-5 title candidates
**优化现有标题**:
```bash
python scripts/optimize_title.py main.tex --optimize
**Optimize Existing Title**:
```bash
python scripts/optimize_title.py main.tex --optimize分析当前标题并提供改进建议
Analyze current title and provide improvement suggestions
**检查标题质量**:
```bash
python scripts/optimize_title.py main.tex --check
**Check Title Quality**:
```bash
python scripts/optimize_title.py main.tex --check根据最佳实践评估标题(评分 0-100)
Evaluate title based on best practices (score 0-100)
**标题质量标准**(基于 GB/T 7713.1-2006 及国际最佳实践):
| 标准 | 权重 | 说明 |
|------|------|------|
| **简洁性** | 25% | 删除"关于...的研究"、"...的探索"、"新型"、"改进的" |
| **可搜索性** | 30% | 核心术语(方法+问题)出现在前 20 字内 |
| **长度** | 15% | 最佳:15-25 字;可接受:10-30 字 |
| **具体性** | 20% | 具体方法/问题名称,避免泛泛而谈 |
| **规范性** | 10% | 符合学位论文标题规范,避免生僻缩写 |
**标题生成工作流**:
**步骤 1:内容分析**
从摘要/引言中提取:
- **研究问题**:解决什么挑战?
- **研究方法**:提出什么方法?
- **应用领域**:什么应用场景?
- **核心贡献**:主要成果是什么?(可选)
**步骤 2:关键词提取**
识别 3-5 个核心关键词:
- 方法关键词:"Transformer"、"图神经网络"、"强化学习"
- 问题关键词:"时间序列预测"、"故障检测"、"图像分割"
- 领域关键词:"工业控制"、"医学影像"、"自动驾驶"
**步骤 3:标题模板选择**
学位论文常用模式:
| 模式 | 示例 | 适用场景 |
|------|------|----------|
| 基于方法的问题研究 | "基于Transformer的时间序列预测方法研究" | 方法创新型 |
| 领域中的问题与方法 | "工业系统故障检测的图神经网络方法" | 应用导向型 |
| 问题的方法及应用 | "时间序列预测的注意力机制及其在工业控制中的应用" | 理论+应用型 |
| 面向领域的方法研究 | "面向智能制造的深度学习预测性维护方法" | 领域专项型 |
**步骤 4:生成标题候选**
生成 3-5 个不同侧重的候选标题:
1. 方法侧重型
2. 问题侧重型
3. 应用侧重型
4. 平衡型(推荐)
5. 简洁变体
**步骤 5:质量评分**
每个候选标题获得:
- 总体评分(0-100)
- 各标准细分评分
- 具体改进建议
**标题优化规则**:
**❌ 删除无效词汇**:
| 避免使用 | 原因 |
|----------|------|
| 关于...的研究 | 冗余(所有论文都是研究) |
| ...的探索 | 冗余且不具体 |
| 新型 / 新颖的 | 发表即意味着新颖 |
| 改进的 / 优化的 | 不具体,需说明如何改进 |
| 基于...的 | 可简化为直接表述 |
**✅ 推荐结构**:好:工业控制系统时间序列预测的Transformer方法
差:关于基于Transformer的工业控制系统时间序列预测的研究
好:图神经网络故障检测方法及其工业应用
差:新型改进的基于图神经网络的故障检测方法研究
好:注意力机制的多变量时间序列预测方法
差:基于注意力机制的改进型多变量时间序列预测模型研究
**关键词布局策略**:
- **前 20 字**:最重要的关键词(方法+问题)
- **避免开头**:"关于"、"对于"、"针对"(可放在中间)
- **优先使用**:名词和技术术语,而非动词和形容词
**缩写使用准则**:
| ✅ 可接受 | ❌ 标题中避免 |
|----------|--------------|
| AI、机器学习、深度学习 | 实验室特定缩写 |
| LSTM、GRU、CNN | 化学分子式(除非极常见) |
| 物联网、5G、GPS | 非标准方法名缩写 |
| DNA、RNA、MRI | 生僻领域专用缩写 |
**学校模板特殊要求**:
**清华大学(thuthesis)**:
- 中文标题:不超过 36 个汉字
- 英文标题:对应中文标题翻译
- 避免使用缩写和公式
- 示例:"深度学习在智能制造预测性维护中的应用研究"
**北京大学(pkuthss)**:
- 中文标题:简明扼要,一般不超过 25 字
- 可使用副标题(用破折号分隔)
- 示例:"图神经网络故障检测方法——面向工业控制系统的研究"
**通用要求(ctexbook)**:
- 遵循 GB/T 7713.1-2006 规范
- 中文标题:15-25 字为宜
- 英文标题:对应翻译,注意冠词和介词
- 示例:"基于Transformer的时间序列预测方法及应用"
**输出格式**:
```latex
% ============================================================
% 标题优化报告
% ============================================================
% 当前标题:"关于基于深度学习的时间序列预测的研究"
% 质量评分:48/100
%
% 检测到的问题:
% 1. [严重] 包含"关于...的研究"(删除冗余词汇)
% 2. [重要] 方法描述过于宽泛("深度学习"太笼统)
% 3. [次要] 长度可接受(18字)但可更具体
%
% 推荐标题(按评分排序):
%
% 1. "工业控制系统时间序列预测的Transformer方法" [评分: 94/100]
% - 简洁性:✅ (19字)
% - 可搜索性:✅ (方法+问题在前15字)
% - 具体性:✅ (Transformer,而非"深度学习")
% - 领域性:✅ (工业控制系统)
% - 规范性:✅ (符合学位论文规范)
%
% 2. "多变量时间序列预测的注意力机制研究" [评分: 89/100]
% - 简洁性:✅ (17字)
% - 可搜索性:✅ (核心术语靠前)
% - 具体性:✅ (注意力机制、多变量)
% - 建议:可考虑添加应用领域
%
% 3. "深度学习时间序列预测方法及其在智能制造中的应用" [评分: 81/100]
% - 简洁性:⚠️ (24字,可接受)
% - 可搜索性:✅
% - 具体性:⚠️ ("深度学习"仍较宽泛)
% - 领域性:✅ (智能制造)
%
% 关键词分析:
% - 主要:Transformer、时间序列、预测
% - 次要:工业控制、注意力、LSTM
% - 可搜索性:"Transformer 时间序列"在知网出现 456 篇(平衡度好)
%
% 建议的 LaTeX 更新:
% \title{工业控制系统时间序列预测的Transformer方法}
% \englishtitle{Transformer-Based Time Series Forecasting for Industrial Control Systems}
% ============================================================中英文标题对照:
标题翻译时需注意:
- 中文"基于X的Y"通常译为 "X-Based Y" 或 "Y via X"
- 避免逐字翻译,保持英文表达习惯
- 英文标题使用 Title Case(主要词首字母大写)
| 中文标题 | 英文标题 |
|---|---|
| 工业系统故障检测的图神经网络方法 | Graph Neural Networks for Fault Detection in Industrial Systems |
| 基于注意力机制的时间序列预测研究 | Attention-Based Time Series Forecasting |
| 深度学习在智能制造中的应用 | Deep Learning Applications in Smart Manufacturing |
交互式模式(推荐):
bash
python scripts/optimize_title.py main.tex --interactive
**Title Quality Standards** (Based on GB/T 7713.1-2006 and international best practices):
| Standard | Weight | Description |
|------|------|------|
| **Conciseness** | 25% | Remove redundant phrases like "关于...的研究" (A study on...), "...的探索" (An exploration of...), "新型" (new type), "改进的" (improved) |
| **Searchability** | 30% | Core terms (method + problem) appear in the first 20 characters |
| **Length** | 15% | Optimal: 15-25 characters; Acceptable: 10-30 characters |
| **Specificity** | 20% | Specific method/problem names, avoid vague statements |
| **Standardization** | 10% | Comply with academic thesis title standards, avoid obscure abbreviations |
**Title Generation Workflow**:
**Step 1: Content Analysis**
Extract from abstract/introduction:
- **Research Problem**: What challenge is being addressed?
- **Research Method**: What method is proposed?
- **Application Field**: What application scenario?
- **Core Contribution**: What are the main outcomes? (Optional)
**Step 2: Keyword Extraction**
Identify 3-5 core keywords:
- Method Keywords: "Transformer", "Graph Neural Network", "Reinforcement Learning"
- Problem Keywords: "Time Series Prediction", "Fault Detection", "Image Segmentation"
- Field Keywords: "Industrial Control", "Medical Imaging", "Autonomous Driving"
**Step 3: Title Template Selection**
Common patterns for academic theses:
| Pattern | Example | Applicable Scenario |
|------|------|----------|
| Research on Problem Based on Method | "Research on Time Series Prediction Method Based on Transformer" | Method innovation |
| Problem and Method in Field | "Graph Neural Network Method for Fault Detection in Industrial Systems" | Application-oriented |
| Method for Problem and Its Application | "Attention Mechanism for Time Series Prediction and Its Application in Industrial Control" | Theory + Application |
| Method Research for Field | "Deep Learning-based Predictive Maintenance Method for Smart Manufacturing" | Field-specific |
**Step 4: Generate Title Candidates**
Generate 3-5 title candidates with different focuses:
1. Method-focused
2. Problem-focused
3. Application-focused
4. Balanced (Recommended)
5. Concise variant
**Step 5: Quality Scoring**
Each candidate title receives:
- Overall score (0-100)
- Sub-scores for each standard
- Specific improvement suggestions
**Title Optimization Rules**:
**❌ Remove Invalid Vocabulary**:
| Avoid Using | Reason |
|----------|------|
| 关于...的研究 (A study on...) | Redundant (all theses are research) |
| ...的探索 (An exploration of...) | Redundant and non-specific |
| 新型 / 新颖的 (New / Novel) | Publication implies novelty |
| 改进的 / 优化的 (Improved / Optimized) | Non-specific; need to explain how it's improved |
| 基于...的 (Based on...) | Can be simplified to direct expression |
**✅ Recommended Structure**:Good: Transformer Method for Time Series Prediction in Industrial Control Systems
Bad: A Study on Time Series Prediction in Industrial Control Systems Based on Transformer
Good: Graph Neural Network Fault Detection Method and Its Industrial Application
Bad: A Study on the New and Improved Graph Neural Network-based Fault Detection Method
Good: Attention Mechanism for Multivariate Time Series Prediction
Bad: A Study on the Improved Multivariate Time Series Prediction Model Based on Attention Mechanism
**Keyword Layout Strategy**:
- **First 20 characters**: Most important keywords (method + problem)
- **Avoid starting with**: "关于" (about), "对于" (for), "针对" (for) (can be placed in the middle)
- **Prefer using**: Nouns and technical terms, rather than verbs and adjectives
**Abbreviation Usage Guidelines**:
| ✅ Acceptable | ❌ Avoid in Titles |
|----------|--------------|
| AI, Machine Learning, Deep Learning | Lab-specific abbreviations |
| LSTM, GRU, CNN | Chemical formulas (unless extremely common) |
| IoT, 5G, GPS | Non-standard method name abbreviations |
| DNA, RNA, MRI | Obscure field-specific abbreviations |
**University Template Special Requirements**:
**Tsinghua University (thuthesis)**:
- Chinese title: No more than 36 Chinese characters
- English title: Corresponding translation of Chinese title
- Avoid abbreviations and formulas
- Example: "Application of Deep Learning in Predictive Maintenance for Smart Manufacturing"
**Peking University (pkuthss)**:
- Chinese title: Concise, generally no more than 25 characters
- Subtitles allowed (separated by em dash)
- Example: "Graph Neural Network Fault Detection Method — Research for Industrial Control Systems"
**General Requirements (ctexbook)**:
- Comply with GB/T 7713.1-2006 standard
- Chinese title: 15-25 characters is optimal
- English title: Corresponding translation, pay attention to articles and prepositions
- Example: "Transformer-Based Time Series Prediction Method and Application"
**Output Format**:
```latex
% ============================================================
% Title Optimization Report
% ============================================================
% Current Title: "A Study on Time Series Prediction Based on Deep Learning"
% Quality Score: 48/100
%
% Detected Issues:
% 1. [Critical] Contains "关于...的研究" (A study on...) (remove redundant phrase)
% 2. [Important] Method description is too broad ("Deep Learning" is too general)
% 3. [Minor] Length is acceptable (18 characters) but can be more specific
%
% Recommended Titles (Sorted by Score):
%
% 1. "Transformer Method for Time Series Prediction in Industrial Control Systems" [Score: 94/100]
% - Conciseness: ✅ (19 characters)
% - Searchability: ✅ (Method + problem in first 15 characters)
% - Specificity: ✅ (Transformer, instead of "Deep Learning")
% - Field Relevance: ✅ (Industrial Control Systems)
% - Standardization: ✅ (Complies with academic thesis standards)
%
% 2. "Attention Mechanism for Multivariate Time Series Prediction" [Score: 89/100]
% - Conciseness: ✅ (17 characters)
% - Searchability: ✅ (Core terms at the beginning)
% - Specificity: ✅ (Attention Mechanism, Multivariate)
% - Suggestion: Consider adding application field
%
% 3. "Deep Learning Time Series Prediction Method and Its Application in Smart Manufacturing" [Score: 81/100]
% - Conciseness: ⚠️ (24 characters, acceptable)
% - Searchability: ✅
% - Specificity: ⚠️ ("Deep Learning" is still too general)
% - Field Relevance: ✅ (Smart Manufacturing)
%
% Keyword Analysis:
% - Primary: Transformer, Time Series, Prediction
% - Secondary: Industrial Control, Attention, LSTM
% - Searchability: "Transformer Time Series" appears in 456 papers on CNKI (good balance)
%
% Suggested LaTeX Update:
% \title{Transformer Method for Time Series Prediction in Industrial Control Systems}
% \englishtitle{Transformer-Based Time Series Forecasting for Industrial Control Systems}
% ============================================================Chinese-English Title Alignment:
When translating titles, note:
- Chinese "基于X的Y" is usually translated as "X-Based Y" or "Y via X"
- Avoid word-for-word translation; maintain English expression habits
- Use Title Case for English titles (capitalize first letter of major words)
| Chinese Title | English Title |
|---|---|
| 工业系统故障检测的图神经网络方法 | Graph Neural Networks for Fault Detection in Industrial Systems |
| 基于注意力机制的时间序列预测研究 | Attention-Based Time Series Forecasting |
| 深度学习在智能制造中的应用 | Deep Learning Applications in Smart Manufacturing |
Interactive Mode (Recommended):
bash
python scripts/optimize_title.py main.tex --interactive逐步引导式标题创建,包含用户输入
Step-by-step guided title creation with user input
**批量模式**(多篇论文):
```bash
python scripts/optimize_title.py chapters/*.tex --batch --output title_report.txt标题对比测试(可选):
bash
python scripts/optimize_title.py main.tex --compare "标题A" "标题B" "标题C"
**Batch Mode** (Multiple Theses):
```bash
python scripts/optimize_title.py chapters/*.tex --batch --output title_report.txtTitle Comparison Test (Optional):
bash
python scripts/optimize_title.py main.tex --compare "Title A" "Title B" "Title C"对比多个标题候选,提供详细评分
Compare multiple title candidates and provide detailed scoring
**最佳实践总结**:
1. **关键词前置**:方法+问题放在前 20 字
2. **具体明确**:"Transformer" > "深度学习" > "机器学习"
3. **删除冗余**:去掉"关于"、"研究"、"新型"、"基于"
4. **控制长度**:目标 15-25 字(中文)
5. **测试可搜索性**:用这些关键词能找到你的论文吗?
6. **避免生僻**:除非是广泛认可的术语(AI、LSTM、CNN)
7. **符合规范**:遵循学校模板和 GB/T 7713.1-2006 标准
参考文档:[GB_STANDARD.md](references/GB_STANDARD.md)、[UNIVERSITIES/](references/UNIVERSITIES/)
---
**Best Practices Summary**:
1. **Keywords First**: Place method + problem in the first 20 characters
2. **Be Specific**: "Transformer" > "Deep Learning" > "Machine Learning"
3. **Remove Redundancy**: Delete "关于" (about), "研究" (study), "新型" (new), "基于" (based on)
4. **Control Length**: Target 15-25 characters (Chinese)
5. **Test Searchability**: Can your thesis be found using these keywords?
6. **Avoid Obscurity**: Only use widely recognized terms (AI, LSTM, CNN)
7. **Comply with Standards**: Follow university templates and GB/T 7713.1-2006 standard
Refer to [GB_STANDARD.md](references/GB_STANDARD.md), [UNIVERSITIES/](references/UNIVERSITIES/)
---完整工作流(可选)
Complete Workflow (Optional)
如需完整审查,按顺序执行:
- 结构映射 → 分析论文结构
- 国标格式检查 → 修复格式问题
- 去AI化编辑 → 降低 AI 写作痕迹
- 学术表达 → 改进表达
- 长难句分析 → 简化复杂句
- 参考文献 → 验证引用
For full review, execute in the following order:
- Structure Mapping → Analyze thesis structure
- National Standard Format Checking → Fix format issues
- De-AI Editing → Reduce AI writing traces
- Academic Expression → Improve expression
- Long & Complex Sentence Analysis → Simplify complex sentences
- Bibliography → Verify citations
输出报告模板
Output Report Template
markdown
undefinedmarkdown
undefinedLaTeX 学位论文审查报告
LaTeX Academic Thesis Review Report
总览
Overview
- 整体状态:✅ 符合要求 / ⚠️ 需要修订 / ❌ 重大问题
- 编译状态:[status]
- 模板类型:[detected template]
- Overall Status: ✅ Compliant / ⚠️ Needs Revision / ❌ Major Issues
- Compilation Status: [status]
- Template Type: [detected template]
结构完整性(X/10 通过)
Structural Completeness (X/10 Pass)
✅ 已完成项
✅ Completed Items
⚠️ 待完善项
⚠️ Items to Be Improved
国标格式审查
National Standard Format Review
✅ 符合项
✅ Compliant Items
❌ 不符合项
❌ Non-Compliant Items
学术表达(N处建议)
Academic Expression (N Suggestions)
[按优先级分组]
[Grouped by Priority]
长难句拆解(M处)
Long & Complex Sentence Analysis (M Items)
[详细分析]
---[Detailed Analysis]
---最佳实践
Best Practices
本技能遵循 Claude Code Skills 最佳实践:
This skill follows Claude Code Skills best practices:
技能设计原则
Skill Design Principles
- 职责单一:每个模块处理一项特定任务(KISS 原则)
- 最小权限:仅请求必要的工具访问权限
- 明确触发:使用特定关键词调用模块
- 结构化输出:所有建议使用统一的 diff-comment 格式
- Single Responsibility: Each module handles one specific task (KISS principle)
- Least Privilege: Only request necessary tool access permissions
- Explicit Trigger: Use specific keywords to call modules
- Structured Output: All suggestions use a unified diff-comment format
使用指南
Usage Guide
- 先检查编译:在进行其他检查前,确保文档能正常编译
- 迭代优化:每次只应用一个模块,便于控制修改范围
- 保护关键元素:绝不修改 、
\cite{}、\ref{}、公式环境\label{} - 提交前验证:接受修改前仔细审查所有建议
- Check Compilation First: Ensure the document can be compiled normally before other checks
- Iterative Optimization: Apply only one module at a time to control modification scope
- Protect Critical Elements: Never modify ,
\cite{},\ref{}, or math environments\label{} - Verify Before Submission: Carefully review all suggestions before accepting modifications
与其他工具集成
Integration with Other Tools
- 配合版本控制(git)跟踪修改历史
- 结合 LaTeX Workshop 实现实时预览
- 导出建议与导师或合作者共同审阅
- Track modification history with version control (git)
- Achieve real-time preview with LaTeX Workshop
- Export suggestions for joint review with supervisors or collaborators
参考文档
Reference Documents
- STRUCTURE_GUIDE.md: 论文结构要求
- GB_STANDARD.md: GB/T 7714 格式规范
- ACADEMIC_STYLE_ZH.md: 中文学术写作规范
- FORBIDDEN_TERMS.md: 受保护术语
- COMPILATION.md: XeLaTeX/LuaLaTeX 编译指南
- UNIVERSITIES/: 学校模板指南
- DEAI_GUIDE.md: 去AI化写作指南与常见模式
- STRUCTURE_GUIDE.md: Thesis structure requirements
- GB_STANDARD.md: GB/T 7714 format specifications
- ACADEMIC_STYLE_ZH.md: Chinese academic writing standards
- FORBIDDEN_TERMS.md: Protected terms
- COMPILATION.md: XeLaTeX/LuaLaTeX compilation guide
- UNIVERSITIES/: University template guides
- DEAI_GUIDE.md: De-AI writing guide and common patterns