agentleFS
vodolaz095vodolaz095/go-mcp-smtp/skills/lint/SKILL.md

lint

Skill0 starsChanged 3 months agoMITView on GitHub

Use when the user needs to run linting on the Go codebase and automatically fix any issues found. The skill should: - Check for required tools before running - Execute make lint command - Parse lint output to identify issues - Apply fixes using appropriate methods (edit, lsp_replace_symbol, etc) - Re-run linting to verify fixes - Handle different types of lint issues appropriately

82 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use query, ingest and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArtemXTechSkill

    query

    Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

    Also in 17 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 26 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 5 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 4 projects that use this

  • AnthropicSkill

    digest

    Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user needs to run linting on the Go codebase and automatically fix any issues found.

    line 3
  2. Distinctive:

    Verify required tools are available (go, gopls, staticcheck)

    line 7
  3. Very specific:

    Run make lint to identify issues

    line 8
  4. Distinctive:

    Verify fixes resolved all issues

    line 10
  5. Distinctive:

    Check for required tools before running

    line 15
  6. Distinctive:

    Must verify go, gopls, and staticcheck are available before running

    line 24
  7. Very specific:

    Must run make lint as the primary lint command

    line 25
  8. Distinctive:

    Must attempt to fix all reported issues

    line 26
  9. Distinctive:

    Must verify fixes by re-running lint

    line 27
  10. Distinctive:

    Should preserve code functionality while improving style

    line 28

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

lint

Use when the user needs to run linting on the Go codebase and automatically fix any issues found.

Usage

  1. Verify required tools are available (go, gopls, staticcheck)
  2. Run make lint to identify issues
  3. Analyze lint output and apply fixes
  4. Verify fixes resolved all issues

Implementation

The skill should:

  • Check for required tools before running
  • Execute make lint command
  • Parse lint output to identify issues
  • Apply fixes using appropriate methods (edit, lsp_replace_symbol, etc)
  • Re-run linting to verify fixes
  • Handle different types of lint issues appropriately

Requirements

  • Must verify go, gopls, and staticcheck are available before running
  • Must run make lint as the primary lint command
  • Must attempt to fix all reported issues
  • Must verify fixes by re-running lint
  • Should preserve code functionality while improving style

Dependencies

  • Go compiler (go)
  • Go language server (gopls)
  • Staticcheck tool
  • Make build system
  • Access to project files

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.