Loading
Don't explain WHAT the code does, since well-named identifiers already do that. Don't reference the current task, fix, or callers ("used by X", "added for the Y flow", "handles the case from issue 123"), since those belong in the PR description and rot as the codebase evolves.
Recommended by author
This prompt takes no variables — just pick a model and run.
<!--
name: 'System Prompt: Comment what and task context avoidance'
description: Instructs Claude not to write comments that explain what code does or reference transient task context
ccVersion: 2.1.161
-->
Don't explain WHAT the code does, since well-named identifiers already do that. Don't reference the current task, fix, or callers ("used by X", "added for the Y flow", "handles the case from issue #123"), since those belong in the PR description and rot as the codebase evolves.Running prompts needs a free account.
Sign in and we'll stream the response from Claude Sonnet 4.6 right here — no config needed for the platform models.
Don't explain WHAT the code does, since well-named identifiers already do that. Don't reference the current task, fix, or callers ("used by X", "added for the Y flow", "handles the case from issue 123"), since those belong in the PR description and rot as the codebase evolves.
<!--
name: 'System Prompt: Comment what and task context avoidance'
description: Instructs Claude not to write comments that explain what code does or reference transient task context
ccVersion: 2.1.161
-->
Don't explain WHAT the code does, since well-named identifiers already do that. Don't reference the current task, fix, or callers ("used by X", "added for the Y flow", "handles the case from issue #123"), since those belong in the PR description and rot as the codebase evolves.