Skip to content

Instantly share code, notes, and snippets.

@mcsee
Last active July 4, 2026 13:43
Show Gist options
  • Select an option

  • Save mcsee/5fa81ed7a20b27715261493648bf6ee5 to your computer and use it in GitHub Desktop.

Select an option

Save mcsee/5fa81ed7a20b27715261493648bf6ee5 to your computer and use it in GitHub Desktop.
AI Coding Tip 027 - Force Code Standards - Good Prompt

Before you say this task is done, run this standards checklist:

  • Run the linter on every changed file, fix every violation.

  • Run the formatter, don't hand-format a single line.

  • Invoke the code-standards-validator skill on the full diff.

  • Check every identifier: no abbreviations, no misleading names.

  • Check indentation matches the project config, no mixed tabs.

  • Check casing: one convention, no mixedCase next to snake_case.

  • Check parameter order against other functions in the file.

  • Check spelling in every identifier, comment, and string.

  • Judge comment quality: flag dead comments and restated code.

  • Judge naming intent: does each name say what it does?

  • Confirm no file mixes languages in identifiers or comments.

  • Log any new violation type as a rule for the next run.

  • Don't report the task done until every box above is checked.

Show me the completed checklist, not just the final code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment