Skip to content

Latest commit

 

History

History
38 lines (25 loc) · 1.42 KB

File metadata and controls

38 lines (25 loc) · 1.42 KB

Agent Instructions

Golang

When editing Go files (*.go):

  • Read .instructions/golang.md and announce once per task that you are following it.
  • Before committing, ensure code is formatted and linted:
    • Run gofmt (or go fmt) and organize imports.
    • Run golangci-lint run at the repository root and address findings.

Markdown

When editing Markdown (*.md, *.mdx):

  • Read .instructions/markdown.md and announce once per task that you are following it.
  • Use proper headings (##, ###), fenced code blocks with language, and keep lines within the configured limit.

PowerShell

When editing PowerShell files (*.ps1, *.psm1, *.psd1):

  • Read .instructions/powershell.md and 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.

Commit and Pull Requests Guidelines

  • Use Conventional Commits for PR titles and commit messages.
  • The repository specific rules are in .commitlintrc.json.
  • Always run gofmt and golangci-lint run before submitting changes.
  • Limit commit message lines to a maximum of 200 characters.

Examples:

  • feat(config): cache remote configs via HEAD check
  • fix(markdown): correct reference link syntax in docs
  • chore(ci): run golangci-lint in build step