write-coding-standards-from-file
Generates a coding standards document by analyzing existing code files, ensuring consistency and adherence to style guidelines.
Install this skill
Security score
The write-coding-standards-from-file skill was audited on Mar 1, 2026 and we found 61 security issues across 2 threat categories, including 38 high-severity. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 14 | Parameters for the prompt have a text definition. There is one required parameter **`${fileName}`**, and several optional parameters **`${folderName}`**, **`${instructions}`**, and any **`[configVaria |
Template literal with variable interpolation in command context
| 27 | - For each file in `${newFileName}`, if file does not exist, use that file name and `break`, else continue to next file name of `${newFileName}`. |
Template literal with variable interpolation in command context
| 44 | - useTemplate = If passed will override the configuration `${useTemplate}` default. Values are `[["v", "verbose"], ["m", "minimal"], ["b", "best fit"]]`. |
Template literal with variable interpolation in command context
| 55 | ### `${fileName}.length > 1 || ${folderName} != undefined` |
Template literal with variable interpolation in command context
| 57 | * If true, toggle `${fixInconsistencies}` to false. |
Template literal with variable interpolation in command context
| 59 | ### `${addToREADME} == true` |
Template literal with variable interpolation in command context
| 62 | * If true, toggle both `${createNewFile}` and `${outputSpecToPrompt}` to false. |
Template literal with variable interpolation in command context
| 64 | ### `${addToREADMEInsertions} == "atBegin"` |
Template literal with variable interpolation in command context
| 66 | * If `${addToREADME}` is true, then insert the coding standards data at the **beginning** of the `README.md` file after the title. |
Template literal with variable interpolation in command context
| 68 | ### `${addToREADMEInsertions} == "middle"` |
Template literal with variable interpolation in command context
| 70 | * If `${addToREADME}` is true, then insert the coding standards data at the **middle** of the `README.md` file, changing the standards title heading to match that of the `README.md` composition. |
Template literal with variable interpolation in command context
| 72 | ### `${addToREADMEInsertions} == "beforeEnd"` |
Template literal with variable interpolation in command context
| 74 | * If `${addToREADME}` is true, then insert the coding standards data at the **end** of the `README.md` file, inserting a new line after the last character, then inserting the data on a new line. |
Template literal with variable interpolation in command context
| 76 | ### `${addToREADMEInsertions} == "bestFitUsingContext"` |
Template literal with variable interpolation in command context
| 78 | * If `${addToREADME}` is true, then insert the coding standards data at the **best fitting line** of the `README.md` file in regards to the context of the `README.md` composition and flow of data. |
Template literal with variable interpolation in command context
| 80 | ### `${addStandardsTest} == true` |
Template literal with variable interpolation in command context
| 84 | ### `${createNewFile} == true` |
Template literal with variable interpolation in command context
| 86 | * Create a new file using the value, or one of the possible values, from `${newFileName}`. |
Template literal with variable interpolation in command context
| 87 | * If true, toggle both `${outputSpecToPrompt}` and `${addToREADME}` to false. |
Template literal with variable interpolation in command context
| 89 | ### `${fetchStyleURL} == true` |
Template literal with variable interpolation in command context
| 92 | * For each relevant item in `### Fetch Links`, run `#fetch ${item}`. |
Template literal with variable interpolation in command context
| 94 | ### `${findInconsistencies} == true` |
Template literal with variable interpolation in command context
| 98 | * Depending on the status of `${fixInconsistencies}`, either edit and fix the low count categories to match the majority, or output to prompt inconsistencies stored in temporary memory. |
Template literal with variable interpolation in command context
| 100 | ### `${fixInconsistencies} == true` |
Template literal with variable interpolation in command context
| 104 | ### `typeof ${newFileName} == "string"` |
Template literal with variable interpolation in command context
| 106 | * If specifically defined as a `string`, create a new file using the value from `${newFileName}`. |
Template literal with variable interpolation in command context
| 108 | ### `typeof ${newFileName} != "string"` |
Template literal with variable interpolation in command context
| 110 | * If **NOT** specifically defined as a `string`, but instead an `object` or an array, create a new file using a value from `${newFileName}` by applying this rule: |
Template literal with variable interpolation in command context
| 111 | - For each file name in `${newFileName}`, if file does not exist, use that file name and `break`, else continue to the next. |
Template literal with variable interpolation in command context
| 113 | ### `${outputSpecToPrompt} == true` |
Template literal with variable interpolation in command context
| 116 | * If true, toggle both `${createNewFile}` and `${addToREADME}` to false. |
Template literal with variable interpolation in command context
| 118 | ### `${useTemplate} == "v" || ${useTemplate} == "verbose"` |
Template literal with variable interpolation in command context
| 122 | ### `${useTemplate} == "m" || ${useTemplate} == "minimal"` |
Template literal with variable interpolation in command context
| 126 | ### `${useTemplate} == "b" || ${useTemplate} == "best"` |
Template literal with variable interpolation in command context
| 128 | * Use either the data under the level three heading `### "v", "verbose"` or `### "m", "minimal"`, depending on the data extracted from `${fileName}`, and use the best fit as guiding template when comp |
Template literal with variable interpolation in command context
| 130 | ### `${useTemplate} == "custom" || ${useTemplate} == "<ANY_NAME>"` |
Template literal with variable interpolation in command context
| 134 | ## **if** `${fetchStyleURL} == true` |
Template literal with variable interpolation in command context
| 136 | Depending on the programming language, for each link in list below, run `#fetch (URL)`, if programming language is `${fileName} == [<Language> Style Guide]`. |
External URL reference
| 140 | - [C Style Guide](https://users.ece.cmu.edu/~eno/coding/CCodingStandard.html) |
External URL reference
| 141 | - [C# Style Guide](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions) |
External URL reference
| 142 | - [C++ Style Guide](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines) |
External URL reference
| 144 | - [Java Style Guide](https://coderanch.com/wiki/718799/Style) |
External URL reference
| 146 | - [jQuery Style Guide](https://contribute.jquery.org/style-guide/js/) |
External URL reference
| 147 | - [JavaScript Style Guide](https://www.w3schools.com/js/js_conventions.asp) |
External URL reference
| 148 | - [JSON Style Guide](https://google.github.io/styleguide/jsoncstyleguide.xml) |
External URL reference
| 149 | - [Kotlin Style Guide](https://kotlinlang.org/docs/coding-conventions.html) |
External URL reference
| 150 | - [Markdown Style Guide](https://cirosantilli.com/markdown-style-guide/) |
External URL reference
| 151 | - [Perl Style Guide](https://perldoc.perl.org/perlstyle) |
External URL reference
| 152 | - [PHP Style Guide](https://phptherightway.com/) |
External URL reference
| 153 | - [Python Style Guide](https://peps.python.org/pep-0008/) |
External URL reference
| 154 | - [Ruby Style Guide](https://rubystyle.guide/) |
External URL reference
| 156 | - [Swift Style Guide](https://www.swift.org/documentation/api-design-guidelines/) |
External URL reference
| 157 | - [TypeScript Style Guide](https://www.typescriptlang.org/docs/handbook/declaration-files/do-s-and-don-ts.html) |
External URL reference
| 158 | - [Visual Basic Style Guide](https://en.wikibooks.org/wiki/Visual_Basic/Coding_Standards) |
External URL reference
| 159 | - [Shell Script Style Guide](https://google.github.io/styleguide/shellguide.html) |
External URL reference
| 162 | - [CSS](https://cssguidelin.es/) |
External URL reference
| 163 | - [Sass Style Guide](https://sass-guidelin.es/) |
External URL reference
| 165 | - [Linux kernel Style Guide](https://www.kernel.org/doc/html/latest/process/coding-style.html) |
External URL reference
| 167 | - [SQL Style Guide](https://www.sqlstyle.guide/) |
External URL reference
| 168 | - [Angular Style Guide](https://angular.dev/style-guide) |
External URL reference
| 169 | - [Vue Style Guide](https://vuejs.org/style-guide/rules-strongly-recommended.html) |