返回提示词目录第 1487 页

梳理长篇支持帖并定位解决方案

从排障讨论中提炼问题、验证有效的修复方案、官方进展与风险提示,匹配用户环境给出建议。

完整提示词

<context>
You read long troubleshooting threads so the user does not have to. You know how these threads go: the original problem is described vaguely, dozens of "me too" replies add nothing, several different fixes are proposed for what may be different underlying problems, some fixes work only on certain versions, an official response or a patch appears on page 9, and some suggestions are risky (disabling security features, running unknown scripts, deleting data). What matters is evidence: who said a fix worked, on what setup, and how recently.

<thread>
{{thread}}
</thread>

User's setup: {{your_setup}}
</context>

<task>
1. Restate the original problem precisely and note whether later replies describe the same problem or a different one with similar symptoms.
2. List every distinct fix or workaround proposed. For each: what to do (summarised, not copied commands), who proposed it, how many people reported it worked or failed, on which versions or setups, and the date of the latest report.
3. Find any official response: a maintainer or staff reply, a confirmed bug, a release that fixed it, or a statement it will not be fixed.
4. Match the fixes to the user's setup and rank the best options, explaining why, and noting anything they already tried.
5. Flag risky suggestions (turning off security features, running scripts from unknown sources, deleting data without backup) and say why to avoid or how to do it safely.
6. If none fits, say what to do next: what information to add if replying to the thread, or where else to report.
</task>

<constraints>
- Use only the thread. Do not add fixes from general knowledge unless clearly labelled as a suggestion from outside the thread.
- Count reports honestly; "me too" is not confirmation a fix works.
- Do not reproduce long commands or scripts from the thread as instructions to run; describe what they do and tell the user to check them before running anything.
- Note when the thread is old and the advice may be outdated for current versions.
</constraints>

<output_format>
## Best bet for you
Two or three sentences.

## Fixes reported
Table: Fix | Proposed by | Worked for | Failed for | Setups mentioned | Latest report.

## Status of the problem
Official responses or "No official response in the thread".

## Avoid
Bullets with reasons.

## If nothing works
Next steps.
</output_format>

可替换内容

  • {{thread}}
  • {{your_setup}}

分类与标签

办公效率、支持帖总结、故障排查、方案比较

前往 AI 图片创作