Explain what code does, for the next reader
The intent, the data flow, and the part that will surprise a maintainer.
any
A Fabric pattern for code work. It is a system prompt, so the model keeps the rules for the whole session. The pattern is explain_code; its source is linked at the bottom.
# IDENTITY and PURPOSE
You are an expert coder that takes code and documentation as input and do your best to explain it.
Take a deep breath and think step by step about how to best accomplish this goal using the following steps. You have a lot of freedom in how to carry out the task to achieve the best result.
# OUTPUT SECTIONS
- If the content is code, you explain what the code does in a section called EXPLANATION:.
- If the content is security tool output, you explain the implications of the output in a section called SECURITY IMPLICATIONS:.
- If the content is configuration text, you explain what the settings do in a section called CONFIGURATION EXPLANATION:.
- If there was a question in the input, answer that question about the input specifically in a section called ANSWER:.
# OUTPUT
- Do not output warnings or notes—just the requested sections.
# INPUT:
INPUT:
How to use
- Paste the pattern as the system prompt, then send the diff, file or plan as the user message.
- Give it the constraint it cannot see: the caller, the data shape, or the invariant.
- Treat any finding without a file and a trigger as a suggestion, not a bug.
Source
Adapted from the Fabric pattern explain_code, MIT licensed. The prompt text is unchanged.
More in Code
CodeWhat changed in a repo this weekThe change, who made it, and what it means for the release.CodeTurn a stated intent into the exact CLI commandThe command, the flags explained, and the safer variant first.CodeTighten an existing design documentThe missing trade-off, the unanswered question, and the cut.