Agent Skills › AjayIrkal23/agentic-mercy-10x › fix-lint-format

fix-lint-format

GitHub

自动检测项目类型并执行格式化和代码检查，确保代码在提交或PR前通过CI构建。支持Go、Node等多语言及Monorepo结构，适配不同仓库规范。

skills/fix-lint-format/SKILL.md AjayIrkal23/agentic-mercy-10x

Trigger Scenarios

修复lint错误解决代码格式化问题提交代码前预检处理CI失败

Install

npx skills add AjayIrkal23/agentic-mercy-10x --skill fix-lint-format -g -y

More Options

Use without installing

npx skills use AjayIrkal23/agentic-mercy-10x@fix-lint-format

指定 Agent (Claude Code)

npx skills add AjayIrkal23/agentic-mercy-10x --skill fix-lint-format -a claude-code -g -y

安装 repo 全部 skill

npx skills add AjayIrkal23/agentic-mercy-10x --all -g -y

预览 repo 内 skill

npx skills add AjayIrkal23/agentic-mercy-10x --list

SKILL.md

Frontmatter

{
    "name": "fix-lint-format",
    "schema": 1,
    "category": "general",
    "surfaces": [
        "general"
    ],
    "triggers": {
        "paths": [],
        "intents": [
            "general"
        ],
        "keywords": [
            "adapts",
            "checks",
            "code",
            "commands",
            "committing",
            "ensure",
            "errors",
            "examples",
            "failures",
            "fix",
            "format",
            "formatting",
            "have",
            "issues",
            "lint",
            "node",
            "passes",
            "project",
            "react",
            "repo",
            "upstream"
        ]
    },
    "platforms": [
        "linux",
        "darwin",
        "windows"
    ],
    "token-cost": 436,
    "description": "Use when you have lint errors, formatting issues, CI failures, or before committing code to ensure it passes project checks. Adapts commands to the repo (Go, Node, React upstream examples)."
}

Fix lint and formatting

Goal

Get the working tree to a state that would pass the project’s automated checks (format, lint, tests where appropriate) before commit or PR.

Portable workflow

Detect the project from the workspace root and changed paths:
- go.mod + Makefile → likely Go; prefer make lint and go test ./... when documented
- package.json → use npm run lint, pnpm lint, or yarn lint as defined in scripts
Format first when the repo documents a formatter (gofmt/goimports, Prettier, etc.)
Lint / static analysis second
Tests for substantial logic changes when quick to run locally

Multi-package / monorepo layouts

If the repository has sibling packages (e.g. client/ and server/, or apps/web and services/api), run each package’s documented lint, format, and test commands from that package’s root—not from a parent folder unless the docs say so. Follow AGENTS.md or README when the repo defines a matrix of commands.

Example — facebook/react monorepo (upstream reference)

From facebook/react fix skill:

Run yarn prettier to fix formatting (repo-specific)
Run yarn linc to check for remaining lint issues
Report any remaining manual fixes

Use this block only when actually working inside the React repository.

Common mistakes

Running a client lint command against server changes (or vice versa)
Assuming npm run preflight exists — prefer reading package.json and Makefile
Ignoring errors that will fail CI — fix or explicitly call out blockers