code-to-thesis
Skill0 starsChanged 21 days agoMITView on GitHub
从已有毕设项目代码中提取论文素材(技术栈、功能模块清单、数据库表、接口清单、核心代码片段、页面截图清单)。已经写完代码、要开始写论文或核对论文与代码是否一致时使用。
In this repository6 other files it gives its agents.
- defense-prepSkill
- requirements-analysisSkill
- system-designSkill
- test-chapterSkill
- thesis-proposalSkill
- thesis-writingSkill
The file
Files
从代码提取论文素材
目标:让论文内容和真实系统一致,避免「论文写了、系统没有」被答辩老师问住。只读代码,不修改项目文件。
步骤
- 技术栈:读
package.json/pom.xml/requirements.txt,列出框架和实际版本号(如 Vue 3.4、Element Plus 2.x),写进「开发环境与技术」小节。 - 功能模块:
- 前端:读路由(
router/index.*、pages.json、菜单配置),得到页面清单 → 按菜单分组成模块。 - 后端:读路由/Controller,列出接口。
- 输出表:模块 | 功能点 | 前端页面 | 后端接口。前端有页面但后端无接口(或反过来)的单独列出,提醒用户确认。
- 前端:读路由(
- 数据库:读建表 SQL、ORM 模型或迁移文件,生成
system-design技能要求的三线表;读外键/关联关系,给出 E-R 关系列表(实体A 1:N 实体B)。 - 接口清单:方法 + 路径 + 鉴权要求 + 简述,核心接口挑 8–15 个进正文。
- 核心代码片段:挑 3–5 段最能体现工作量的(权限校验、统计查询、算法、支付/上传),每段 ≤ 30 行,删掉无关样板,配一段解释。不要贴整文件。
- 截图清单:按模块列出需要截图的页面路径和要展示的状态(列表有数据、弹窗打开、校验提示),让用户自己运行系统截图——不要生成假截图。
- 安全提醒:素材里去掉真实密钥、数据库密码、服务器 IP、真实用户数据。
输出
一个 thesis-materials.md(放在用户指定位置,默认项目根目录下 docs/,写之前先告诉用户路径),分为上面 6 部分。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

