Turn a code pattern fixed in a pull request into a custom Go linter, a tool that checks code without running it. Covers a focused detection rule, tests, and registration in the linter runner.
Generate a new pkg/linters analyzer from a merged or open PR pattern.
Review the instructions the agent will receive before you install.
Use this skill when a user asks to create a new custom Go linter based on a code pattern fixed in a pull request.
Convert one concrete PR pattern into a new go/analysis linter under pkg/linters/<name>/ with tests and runner registration.
pkg/linters/ already covers it.pkg/linters/<name>/<name>.go with exported Analyzerpkg/linters/<name>/<name>_test.go using analysistestpkg/linters/<name>/testdata/src/<name>/<name>.go fixtures with // wantcmd/linters/main.go registration in multichecker.Main(...)go test ./pkg/linters/<name>/...go build ./cmd/lintersmake golint-customFor PR #33038 (Refactor pkg mutex sites to use deferred unlocks consistently), derive a linter idea that reports lock/unlock sections that manually unlock instead of deferring unlock immediately after lock when the function body matches the same cache/logger-style critical section pattern.
pkg/linters/<name>/ and cmd/linters/main.go.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.