3 results for “documentation”
Write an enthusiastic, well-structured PR description for the current changes. Use when the user is about to open a pull request and says "write a PR description", "describe these changes", or "hype up this PR".
Explain a piece of code, concept, or system in plain English with zero assumed knowledge. Use when the user is confused, new to a codebase, or says "I have no idea what this does", "explain this to me", or "ELI5".
Generate a structured mental model of an unfamiliar codebase — entry points, data flow, key abstractions, and gotchas. Use when starting on a new repo, when the user says "explain this codebase", "how does this work", "onboard me", or before making large changes to unfamiliar code.