Write Coding Standards From File

Takes your existing codebase and reverse-engineers a proper coding standards document by analyzing actual syntax patterns across your files. It counts indentation styles, naming conventions, comment formats, and quotation usage to determine what your team actually does versus what you think you do. Generates CONTRIBUTING.md, STYLE.md, or similar files with specific rules based on majority patterns it finds. The inconsistency detection is honestly the most useful part since it will call out mixed tabs and spaces or inconsistent naming that code reviews miss. Works on single files or entire folders, though it gets less opinionated about fixes when analyzing multiple files with conflicting styles.

skills.sh installs: 9.6K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill write-coding-standards-from-file --agent claude-code

Installs into .claude/skills of the current project.

Files

Write Coding Standards From File

Use the existing syntax of the file(s) to establish the standards and style guides for the project. If more than one file or a folder is passed, loop through each file or files in the folder, appending the file's data to temporary memory or a file, then when complete use temporary data as a single instance; as if it were the file name to base the standards and style guideline on.

Rules and Configuration

Below is a set of quasi-configuration boolean and string[] variables. Conditions for handling true, or other values for each variable are under the level two heading ## Variable and Parameter Configuration Conditions.

Parameters for the prompt have a text definition. There is one required parameter ${fileName}, and several optional parameters ${folderName}, ${instructions}, and any [configVariableAsParameter].