When editing Go files (*.go):
- Read
.instructions/golang.mdand announce once per task that you are following it. - Before committing, ensure code is formatted and linted:
- Run
gofmt(orgo fmt) and organize imports. - Run
golangci-lint runat the repository root and address findings.
- Run
When editing Markdown (*.md, *.mdx):
- Read
.instructions/markdown.mdand announce once per task that you are following it. - Use proper headings (
##,###), fenced code blocks with language, and keep lines within the configured limit.
When editing PowerShell files (*.ps1, *.psm1, *.psd1):
- Read
.instructions/powershell.mdand announce once per task that you are following it. - Follow PowerShell best practices for naming, formatting, and error handling.
- Include comment-based help for public functions and ensure proper parameter validation.
- Use Conventional Commits for PR titles and commit messages.
- The repository specific rules are in
.commitlintrc.json. - Always run
gofmtandgolangci-lint runbefore submitting changes. - Limit commit message lines to a maximum of 200 characters.
Examples:
feat(config): cache remote configs via HEAD checkfix(markdown): correct reference link syntax in docschore(ci): run golangci-lint in build step