【开源自荐】LiuNengAI 报错求助整理器：单文件离线，把复现信息整理成 Markdown
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- content
Research direction
This is a project self-submission for a weekly newsletter, not a code change: first look at how the repository records each weekly issue (the most recent issue or Markdown entry) to learn the required entry format. Done means an entry following that format with the project name, links and introduction, plus honoring the disclosure paragraph. Note the outcome depends on maintainer acceptance, and no file or entry point is named in the payload, so scope is judgment-driven.
Written by the indexing model from the issue text.
Description
1). 项目名称：LiuNengAI 报错求助整理器
2). 项目地址：
- 源码：https://github.com/a941249849/liunengai-debug-report
- 在线使用：https://liunenglabs.xyz/guides/debug-report/
- MIT 单文件离线版：https://github.com/a941249849/liunengai-debug-report/releases/tag/v1.0.0
3). 项目简介（100 字以内）：
一个中文单文件网页，把目标、环境、复现步骤、原始报错、尝试方法和希望获得的帮助整理成 Markdown。免费、免登录、输入本地处理，可下载离线使用；不调用 AI，也不执行代码。
4). 推荐原因：
给同学、助教、项目同事或开源维护者提问时，常见问题是只贴一句“报错了”，缺少可复现信息。这个小工具提供六个输入区和一个可编辑输出区，帮助把已知信息写清楚，核对后再复制或下载 .md。它只整理用户输入，不猜诊断结果，不代写作业。页面不保存草稿，关闭前需自行复制；分享前须人工删除密码、密钥、Cookie 和个人信息，没有自动脱敏功能。
工具页不含统计脚本，不上传填写内容，无后端或外部依赖。导航到其他页面时适用那些页面的规则。源码与离线 HTML 均可自行检查、修改和部署。
5). 项目流程图：
flowchart LR
A[填写已知的目标与报错信息] --> B[浏览器本地整理 Markdown]
B --> C[人工核对复现步骤并删除敏感信息]
C --> D[复制或下载说明]
D --> E[自行选择求助对象]
披露：我是 LiuNengAI 运营方，本项目与投稿说明使用了 AI 辅助。网站另有付费 ChatGPT 个人订阅充值业务，属于独立服务方，非 OpenAI 官方；使用此免费工具无需购买，也不需要 AI 订阅。这里只自荐免费开源项目，是否适合周刊由维护者判断。
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenGithubs/weekly
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenGithubs/weekly#157 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
OpenGithubs/weekly#128 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenGithubs/weekly#106 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 22/100
OpenGithubs/weekly#162 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
OpenGithubs/weekly#161 ·
All issues in OpenGithubs/weekly
Similar issues
-
⚠ needs intervention document structure changed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
community documentation first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 70/100
lingdojo/kana-dojo#31864 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
cline/mcp-marketplace#2866 ·
-
list-request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Uniswap/tokenlists-org#3325 ·
-
New App Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ThatGuySam/doesitarm#1104 · 1 comment ·