write-coding-standards-from-file
Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.
Profile →npx skills add github/awesome-copilot --skill write-coding-standards-from-file --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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]`**. ### Configuration Variables * addStandardsTest = false; * addToREADME = false; * addToREADMEInsertions = ["atBegin", "middle", "beforeEnd", "bestFitUsingContext"]; - Default to **beforeEnd**. * createNewFile = true; * fetchStyleURL = true; * findInconsistencies = true; * fixInconsistencies = true; * newFileN
- Rules and Configuration
- Configuration Variables
- Configuration Variables as Prompt Parameters
- Prompt Parameters
- Variable and Parameter Configuration Conditions
- ${fileName}.length > 1 || ${folderName} != undefined
- ${addToREADME} == true
- ${addToREADMEInsertions} == "atBegin"
- ${addToREADMEInsertions} == "middle"
- ${addToREADMEInsertions} == "beforeEnd"
- ${addToREADMEInsertions} == "bestFitUsingContext"
- ${addStandardsTest} == true
- ${createNewFile} == true
- ${fetchStyleURL} == true
What does the write-coding-standards-from-file skill do?
Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.
How do I install it?
Run `npx skills add github/awesome-copilot --skill write-coding-standards-from-file --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.