fxa-explain-code

To explain code changes clearly, detail what the diff does, why the change was made, and any non-obvious implications. Focus on how the change fits into the surrounding system and highlight design decisions.

Reviewing code diffs for gotches involves aligning the changes with project conventions and related documentation. This approach identifies potential pitfalls and edge cases by focusing on the implications of the design decisions.

Documenting design decisions in a code review requires explaining why the change was made, including the specific trade-offs involved. It should also provide references to related files and documentation when useful for context.

Yes, you can analyze architecture across a codebase diff by summarizing what the code does and how it fits into the surrounding system. This includes detailing the rationale behind the changes and identifying potential risks.

Yes, this approach is specifically designed for experienced engineers, focusing on design decisions, trade-offs, and non-obvious implications rather than basic syntax. It highlights what changed, why it was done, and potential edge cases.

You should include references to related files and documentation when useful to provide context for the design decisions. This helps experienced engineers understand how the change fits into the surrounding system architecture.