New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

PR To Go Linter

by github in github/gh-aw

Generate a new pkg/linters analyzer from a merged or open PR pattern.

OfficialMITAuto-check passedDevelopment

Install PR To Go Linter

skills CLI
$ npx skills add github/gh-aw --skill pr-to-go-linter -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/gh-aw pr-to-go-linter --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/gh-aw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/pr-to-go-linter .claude/skills/pr-to-go-linter && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-to-go-linter
GitHub stars
5.3k
Token cost
~479 tokens
SKILL.md length
230 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
MIT

At a glance

Generate a new pkg/linters analyzer from a merged or open PR pattern.

  • Works in 6 steps: Read PR metadata and changed files. → Read the PR diff and extract the… → Define one precise diagnostic rule from… → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers Goal, Inputs, Workflow and Rule quality checks, plus 2 more sections
  • Calls go and make

What it does

PR To Go Linter is an agent skill from github/gh-aw, published by the product's own GitHub organization. Generate a new pkg/linters analyzer from a merged or open PR pattern.

Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Linting and formatting. The repository describes itself as: GitHub Agentic Workflows. The licence is MIT.

When your agent uses it

  • Tasks that involve Linting and formatting

Example prompts

  • “/pr-to-go-linter”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read PR metadata and changed files.
  2. Read the PR diff and extract the repeated pattern that was fixed.
  3. Define one precise diagnostic rule from that pattern.
  4. Confirm no existing linter in pkg/linters/ already covers it.
  5. Implement
  6. Validate

What it can do on your machine

Read from SKILL.md and the folder at commit eb63040. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR To Go Linter loads about 479 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 230 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~479

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/gh-aw at commit eb63040, republished under its MIT licence (© github). 230 words, ~479 tokens.

Download SKILL.mdSave it as .claude/skills/pr-to-go-linter/SKILL.md (or your agent's skills folder).
name
pr-to-go-linter
description
Generate a new pkg/linters analyzer from a merged or open PR pattern.

PR to Go Linter

Use this skill when a user asks to create a new custom Go linter based on a code pattern fixed in a pull request.

Goal

Convert one concrete PR pattern into a new go/analysis linter under pkg/linters/<name>/ with tests and runner registration.

Inputs

  • Repository owner/name
  • Pull request number
  • Target linter name (kebab-case)

Workflow

  1. Read PR metadata and changed files.
  2. Read the PR diff and extract the repeated pattern that was fixed.
  3. Define one precise diagnostic rule from that pattern.
  4. Confirm no existing linter in pkg/linters/ already covers it.
  5. Implement:
    • pkg/linters/<name>/<name>.go with exported Analyzer
    • pkg/linters/<name>/<name>_test.go using analysistest
    • pkg/linters/<name>/testdata/src/<name>/<name>.go fixtures with // want
    • cmd/linters/main.go registration in multichecker.Main(...)
  6. Validate:
    • go test ./pkg/linters/<name>/...
    • go build ./cmd/linters
    • make golint-custom

Rule quality checks

  • High signal, low false positives on this repository.
  • Diagnostic is specific and fixable.
  • Rule scope matches code in the PR (do not generalize beyond evidence).
  • Do not change unrelated linter packages.

Example pattern source

For 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.

Output expectations

  • Minimal implementation-only diff in pkg/linters/<name>/ and cmd/linters/main.go.
  • Tests prove both flagged and non-flagged cases.
  • PR summary explains: source PR, extracted pattern, and why the rule is safe.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/pr-to-go-linter of github/gh-aw.

Open the folder on GitHubat commit eb63040

Compare with similar skills

PR To Go Linter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR To Go Linter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR To Go Linter this skillgithub/gh-aw5.3k—~479Automated safety check: PassMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.2k—~2.2kAutomated safety check: PassMIT
Babysit PR To Pass CIsgl-project/sglang37k2 repos~3kAutomated safety check: PassApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
Go Pedantrychromedp/chromedp13k—~3.7kAutomated safety check: PassMIT
Kedro Babysitkedro-org/kedro11k—~4kAutomated safety check: PassCustom licence

Similar skills

  • Install Anti-Slop Oxlint Rules

    dmmulroy/anti-slop

    Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.2k GitHub stars~2.2k tokensUpdated 27 days ago
    DevelopmentAuto-check passed

  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-check passed

  • Rust Best Practices

    farm-fe/farm

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Kedro Babysit

    kedro-org/kedro

    Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…

    11k GitHub stars~4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • WooCommerce Markdown Guidelines

    woocommerce/woocommerce

    Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks.

    11k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed

More from github/gh-aw

All 52 skills in this repo

  • playwright-cli Browser Automation

    github/gh-aw

    Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Auto-check passed

  • Operational Value Designer

    github/gh-aw

    Official

    Designs and verifies a deterministic grader that measures whether a GitHub Agentic Workflow run reached its real-world or repository outcome.

    5.3k GitHub stars~6.8k tokensUpdated today
    Auto-check passed

  • Copilot Canvas Extension Author

    github/gh-aw

    Official

    Scaffolds, edits, reloads and debugs a canvas extension that the GitHub Copilot CLI can open in its side panel.

    5.3k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • GitHub Copilot PR Finisher

    github/gh-aw

    Official

    Drives an open pull request to merge-ready from inside a GitHub Copilot cloud agent, resolving review threads and local checks concurrently, without merging or retriggering CI.

    5.3k GitHub stars~3.8k tokensUpdated today
    Auto-check: warnings

  • gh-aw Firewall Release Integrator

    github/gh-aw

    Official

    Bumps gh-aw's pinned gh-aw-firewall version, rebuilds generated artifacts, and flags upstream spec or schema changes that need follow-up work.

    5.3k GitHub stars~899 tokensUpdated today
    Auto-check passed

  • gh-aw Console Rendering Tags

    github/gh-aw

    Official

    Guide to the console struct tag system in gh-aw: headers, titles, number and cost formats, omitempty, and how structs, slices and maps render in the terminal.

    5.3k GitHub stars~736 tokensUpdated today
    Auto-check passed

Categories

Questions about PR To Go Linter

What does PR To Go Linter do?

Generate a new pkg/linters analyzer from a merged or open PR pattern. PR To Go Linter is an agent skill from github/gh-aw, published by the product's own GitHub organization. Generate a new pkg/linters analyzer from a merged or open PR pattern.

When should I use PR To Go Linter?

PR To Go Linter fits situations like: tasks that involve Linting and formatting.

How do I install PR To Go Linter in Claude Code?

Run `npx skills add github/gh-aw --skill pr-to-go-linter -a claude-code`. Or copy the skill folder (.github/skills/pr-to-go-linter in github/gh-aw) into .claude/skills/pr-to-go-linter in your project. Claude Code loads it when a task matches its description.

How do I install PR To Go Linter in Codex?

Run `npx skills add github/gh-aw --skill pr-to-go-linter -a codex`. Or copy the skill folder (.github/skills/pr-to-go-linter in github/gh-aw) into .agents/skills/pr-to-go-linter in your project. Codex loads it when a task matches its description.

Can I use PR To Go Linter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/gh-aw --skill pr-to-go-linter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-to-go-linter, .gemini/skills/pr-to-go-linter, .github/skills/pr-to-go-linter and .opencode/skills/pr-to-go-linter in your project.

What does PR To Go Linter need to run?

Going by SKILL.md and its folder, PR To Go Linter needs the command-line tools its instructions call (go and make).

Does PR To Go Linter access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is PR To Go Linter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR To Go Linter use?

PR To Go Linter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR To Go Linter use?

About 479 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR To Go Linter?

Skills that share tags, products or a category with PR To Go Linter: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars), Rust Best Practices (farm-fe/farm, 5.6k stars) and Go Pedantry (chromedp/chromedp, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR To Go Linter?

github (a GitHub organization, an official publisher) maintains it in github/gh-aw, which has 5,350 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/gh-aw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.