Back to search
Top Contributors
A style guide that describes how I want my PowerShell written. For use by both humans and LLMs/agents.
Stars
7
Forks
2
Watchers
7
Open Issues
0
Overall repository health assessment
No package.json found
This might not be a Node.js project
chore: update generated style guide artifacts [skip ci]
0e3180bView on GitHubMerge pull request #73 from franklesniak/copilot/update-style-guide-validation
f76e133View on GitHubFix scope terminology: drop 'modern' to avoid conflating [Modern] scope tag (5.1+/7.x+) with v2.0+ section scope
6165d48View on GitHubAdd [ValidateNotNullOrEmpty()] guidance for mandatory [string] parameters and update checklist
1430a9aView on GitHubchore: update generated style guide artifacts [skip ci]
492ff04View on GitHubMerge pull request #72 from franklesniak/copilot/update-style-guide-catch-blocks
e41f706View on GitHubFix RuntimeException wording and add intentional-translation clarification in Rethrow Anti-Pattern
72a3a3fView on GitHubAdd rethrow anti-pattern warnings and exception-wrapping guidance to Modern catch Block Requirements
22fc85bView on GitHubMerge pull request #69 from franklesniak/copilot/update-local-variable-naming
c6cfe68View on GitHubRename remaining $versionPS to $versionPowerShell in code examples
1b7b8daView on GitHubSpell out $versionPS as $versionPowerShell in naming convention section
1530b79View on GitHubClarify that no-abbreviation rule applies to descriptive portion, not type prefixes
5345878View on GitHubClarify obj as default type prefix and rename hashtable prefix from hash to hashtable
7920548View on GitHub