[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74PV2ADSASB308P55P8EFDJ":3,"skill-same:01M74PV2ADSASB308P55P8EFDJ":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M74PV2ADSASB308P55P8EFDJ","lint",null,"Lint and format code. Auto-detects ESLint, Biome, Prettier, or language-native formatters and runs them with auto-fix. Reports remaining issues with actionable suggestions.","cmetech\u002Fotto-cli","cmetech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F118027304?v=4","01M74PNNHCP8T9GH9NWAWHK66N","Corey Ellis","01M74PNNJ1JR5BJQG3JK95RVFT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Flint\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: lint\ndescription: Lint and format code. Auto-detects ESLint, Biome, Prettier, or language-native formatters and runs them with auto-fix. Reports remaining issues with actionable suggestions.\n---\n\n\u003Cobjective>\nLint and format code in the current project. Auto-detect the project's linter and formatter toolchain, run them against the target files, and report results grouped by severity with actionable fix suggestions.\n\u003C\u002Fobjective>\n\n\u003Cworking_directory_awareness>\n**Before running any `git` or build command:** check whether your dispatch context specifies a working directory (look for \"Working directory:\" in your initial prompt). If it does and `pwd` does not match it, prefix every git invocation with `-C \u003Cthat path>` (e.g. `git -C \u002Fpath\u002Fto\u002Fworktree diff --name-only`) and run linters\u002Fformatters with the explicit path argument. Linting the wrong directory is a silent failure mode.\n\u003C\u002Fworking_directory_awareness>\n\n\u003Carguments>\nThis skill accepts optional arguments after `\u002Flint`:\n\n- **No arguments**: Lint only files changed in the current working tree (`git diff --name-only` and `git diff --cached --name-only`).\n- **A file or directory path**: Lint only that specific path (e.g., `\u002Flint src\u002Futils`).\n- **`--fix`**: Automatically apply safe fixes. Can be combined with a path (e.g., `\u002Flint src\u002F --fix`).\n- **`--fix` without a path**: Auto-fix changed files only.\n\nParse the arguments before proceeding. If `--fix` is present, set fix mode. If a non-flag argument is present, treat it as the target path.\n\u003C\u002Farguments>\n\n\u003Cdetection>\nAuto-detect the project's linter and formatter by checking configuration files in the project root. Check in this order and use the **first match found** for each category (linter vs. formatter). A project may have both a linter and a formatter.\n\n**JavaScript\u002FTypeScript Linters:**\n\n1. **Biome** — Look for `biome.json` or `biome.jsonc` in the project root.\n   - Lint command: `npx @biomejs\u002Fbiome check .` (or `--apply` with `--fix`)\n   - Format command: `npx @biomejs\u002Fbiome format .` (or `--write` with `--fix`)\n   - Biome handles both linting and formatting. No need for a separate formatter if Biome is detected.\n\n2. **ESLint** — Look for `.eslintrc`, `.eslintrc.*` (js, cjs, json, yml, yaml), `eslint.config.*` (js, mjs, cjs, ts, mts, cts), or an `\"eslintConfig\"` key in `package.json`.\n   - Lint command: `npx eslint .` (or `--fix` with `--fix`)\n   - Check `package.json` for the installed version. ESLint 9+ uses flat config (`eslint.config.*`).\n\n**JavaScript\u002FTypeScript Formatters (only if Biome was NOT detected):**\n\n3. **Prettier** — Look for `.prettierrc`, `.prettierrc.*`, `prettier.config.*`, or a `\"prettier\"` key in `package.json`.\n   - Format check: `npx prettier --check .`\n   - Format fix: `npx prettier --write .`\n\n**Rust:**\n\n4. **rustfmt** — Look for `rustfmt.toml` or `.rustfmt.toml`, or `Cargo.toml` in the project root.\n   - Format check: `cargo fmt -- --check`\n   - Format fix: `cargo fmt`\n   - Lint: `cargo clippy` (if available)\n\n**Go:**\n\n5. **Go tools** — Look for `go.mod` in the project root.\n   - Format check: `gofmt -l .`\n   - Format fix: `gofmt -w .`\n   - Lint: `golangci-lint run` (if installed), otherwise `go vet .\u002F...`\n\n**Python:**\n\n6. **Ruff** — Look for `ruff.toml` or a `[tool.ruff]` section in `pyproject.toml`.\n   - Lint command: `ruff check .` (or `--fix` with `--fix`)\n   - Format command: `ruff format .` (or `--check` without `--fix`)\n\n7. **Black** — Look for a `[tool.black]` section in `pyproject.toml`, or `black` in requirements files.\n   - Format check: `black --check .`\n   - Format fix: `black .`\n\nIf no linter or formatter is detected, inform the user and suggest common options for their project type based on the files present.\n\u003C\u002Fdetection>\n\n\u003Cexecution>\n\n**Step 1: Determine target files**\n\n- If a path argument was provided, use that path.\n- If no path argument, get changed files:\n  ```bash\n  git diff --name-only\n  git diff --cached --name-only\n  ```\n  Filter to files that still exist on disk. If no files are changed, inform the user and offer to lint the entire project instead.\n\n**Step 2: Run the detected tools**\n\nRun the linter and\u002For formatter against the target files or directory.\n\n- **Without `--fix`**: Run in check\u002Freport mode only. Do NOT modify any files.\n- **With `--fix`**: Run with auto-fix flags enabled.\n\nWhen running formatters without `--fix`, show a preview of what would change:\n- For Prettier: use `--check` and list files that would change.\n- For Biome: use `check` without `--apply`.\n- For Black: use `--check --diff` to show the diff preview.\n- For Ruff: use `--diff` for format and standard output for lint.\n- For rustfmt\u002Fgofmt: use `--check` or `-l` to list files, then show a diff for up to 5 files using `diff \u003C(command) file`.\n\n**Step 3: Parse and organize output**\n\nParse the tool output and organize issues:\n\n```markdown\n## Lint Results\n\n### Errors (X issues)\n| File | Line | Rule | Message |\n|------|------|------|---------|\n| ... | ... | ... | ... |\n\n### Warnings (X issues)\n| File | Line | Rule | Message |\n|------|------|------|---------|\n| ... | ... | ... | ... |\n\n### Formatting\n- X files would be reformatted\n- [list files]\n\n### Summary\n- Total issues: X errors, Y warnings, Z formatting\n- Auto-fixable: N issues (run `\u002Flint --fix` to apply)\n```\n\n**Step 4: Suggest fixes for common issues**\n\nFor the most frequent issues, provide brief actionable guidance:\n\n- If the same rule appears 5+ times, suggest a bulk fix or config change.\n- For unused imports\u002Fvariables, list them for quick removal.\n- For formatting-only issues, note that `--fix` will resolve them safely.\n- For issues that cannot be auto-fixed, provide a one-line explanation of how to resolve each unique rule violation.\n\n\u003C\u002Fexecution>\n\n\u003Ccritical_rules>\n\n1. **Never modify files without `--fix`**: Default mode is report-only. Respect the user's working tree.\n2. **Use the project's own config**: Do not invent lint rules. Use whatever config files exist in the project.\n3. **Use the project's installed version**: Always prefer `npx`, `cargo`, or the project-local binary. Do not use globally installed tools unless no local version exists.\n4. **Handle missing tools gracefully**: If a config file exists but the tool is not installed, inform the user and provide the install command (e.g., `npm install --save-dev eslint`).\n5. **Respect `.gitignore` and ignore patterns**: Do not lint `node_modules`, `dist`, `build`, `target`, `.git`, or other commonly ignored directories. Most tools handle this automatically; verify they do.\n6. **Limit output**: If there are more than 50 issues, show the first 30 grouped by severity, then summarize the rest with counts per file. Do not flood the user with hundreds of lines.\n7. **Exit cleanly**: After presenting results, do not take further action. Let the user decide next steps.\n\n\u003C\u002Fcritical_rules>\n","\u003Cobjective>\nLint and format code in the current project. Auto-detect the project's linter and formatter toolchain, run them against the target files, and report results grouped by severity with actionable fix suggestions.\n\u003C\u002Fobjective>\n\n\u003Cworking_directory_awareness>\n**Before running any `git` or build command:** check whether your dispatch context specifies a working directory (look for \"Working directory:\" in your initial prompt). If it does and `pwd` does not match it, prefix every git invocation with `-C \u003Cthat path>` (e.g. `git -C \u002Fpath\u002Fto\u002Fworktree diff --name-only`) and run linters\u002Fformatters with the explicit path argument. Linting the wrong directory is a silent failure mode.\n\u003C\u002Fworking_directory_awareness>\n\n\u003Carguments>\nThis skill accepts optional arguments after `\u002Flint`:\n\n- **No arguments**: Lint only files changed in the current working tree (`git diff --name-only` and `git diff --cached --name-only`).\n- **A file or directory path**: Lint only that specific path (e.g., `\u002Flint src\u002Futils`).\n- **`--fix`**: Automatically apply safe fixes. Can be combined with a path (e.g., `\u002Flint src\u002F --fix`).\n- **`--fix` without a path**: Auto-fix changed files only.\n\nParse the arguments before proceeding. If `--fix` is present, set fix mode. If a non-flag argument is present, treat it as the target path.\n\u003C\u002Farguments>\n\n\u003Cdetection>\nAuto-detect the project's linter and formatter by checking configuration files in the project root. Check in this order and use the **first match found** for each category (linter vs. formatter). A project may have both a linter and a formatter.\n\n**JavaScript\u002FTypeScript Linters:**\n\n1. **Biome** — Look for `biome.json` or `biome.jsonc` in the project root.\n   - Lint command: `npx @biomejs\u002Fbiome check .` (or `--apply` with `--fix`)\n   - Format command: `npx @biomejs\u002Fbiome format .` (or `--write` with `--fix`)\n   - Biome handles both linting and formatting. No need for a separate formatter if Biome is detected.\n\n2. **ESLint** — Look for `.eslintrc`, `.eslintrc.*` (js, cjs, json, yml, yaml), `eslint.config.*` (js, mjs, cjs, ts, mts, cts), or an `\"eslintConfig\"` key in `package.json`.\n   - Lint command: `npx eslint .` (or `--fix` with `--fix`)\n   - Check `package.json` for the installed version. ESLint 9+ uses flat config (`eslint.config.*`).\n\n**JavaScript\u002FTypeScript Formatters (only if Biome was NOT detected):**\n\n3. **Prettier** — Look for `.prettierrc`, `.prettierrc.*`, `prettier.config.*`, or a `\"prettier\"` key in `package.json`.\n   - Format check: `npx prettier --check .`\n   - Format fix: `npx prettier --write .`\n\n**Rust:**\n\n4. **rustfmt** — Look for `rustfmt.toml` or `.rustfmt.toml`, or `Cargo.toml` in the project root.\n   - Format check: `cargo fmt -- --check`\n   - Format fix: `cargo fmt`\n   - Lint: `cargo clippy` (if available)\n\n**Go:**\n\n5. **Go tools** — Look for `go.mod` in the project root.\n   - Format check: `gofmt -l .`\n   - Format fix: `gofmt -w .`\n   - Lint: `golangci-lint run` (if installed), otherwise `go vet .\u002F...`\n\n**Python:**\n\n6. **Ruff** — Look for `ruff.toml` or a `[tool.ruff]` section in `pyproject.toml`.\n   - Lint command: `ruff check .` (or `--fix` with `--fix`)\n   - Format command: `ruff format .` (or `--check` without `--fix`)\n\n7. **Black** — Look for a `[tool.black]` section in `pyproject.toml`, or `black` in requirements files.\n   - Format check: `black --check .`\n   - Format fix: `black .`\n\nIf no linter or formatter is detected, inform the user and suggest common options for their project type based on the files present.\n\u003C\u002Fdetection>\n\n\u003Cexecution>\n\n**Step 1: Determine target files**\n\n- If a path argument was provided, use that path.\n- If no path argument, get changed files:\n  ```bash\n  git diff --name-only\n  git diff --cached --name-only\n  ```\n  Filter to files that still exist on disk. If no files are changed, inform the user and offer to lint the entire project instead.\n\n**Step 2: Run the detected tools**\n\nRun the linter and\u002For formatter against the target files or directory.\n\n- **Without `--fix`**: Run in check\u002Freport mode only. Do NOT modify any files.\n- **With `--fix`**: Run with auto-fix flags enabled.\n\nWhen running formatters without `--fix`, show a preview of what would change:\n- For Prettier: use `--check` and list files that would change.\n- For Biome: use `check` without `--apply`.\n- For Black: use `--check --diff` to show the diff preview.\n- For Ruff: use `--diff` for format and standard output for lint.\n- For rustfmt\u002Fgofmt: use `--check` or `-l` to list files, then show a diff for up to 5 files using `diff \u003C(command) file`.\n\n**Step 3: Parse and organize output**\n\nParse the tool output and organize issues:\n\n```markdown\n## Lint Results\n\n### Errors (X issues)\n| File | Line | Rule | Message |\n|------|------|------|---------|\n| ... | ... | ... | ... |\n\n### Warnings (X issues)\n| File | Line | Rule | Message |\n|------|------|------|---------|\n| ... | ... | ... | ... |\n\n### Formatting\n- X files would be reformatted\n- [list files]\n\n### Summary\n- Total issues: X errors, Y warnings, Z formatting\n- Auto-fixable: N issues (run `\u002Flint --fix` to apply)\n```\n\n**Step 4: Suggest fixes for common issues**\n\nFor the most frequent issues, provide brief actionable guidance:\n\n- If the same rule appears 5+ times, suggest a bulk fix or config change.\n- For unused imports\u002Fvariables, list them for quick removal.\n- For formatting-only issues, note that `--fix` will resolve them safely.\n- For issues that cannot be auto-fixed, provide a one-line explanation of how to resolve each unique rule violation.\n\n\u003C\u002Fexecution>\n\n\u003Ccritical_rules>\n\n1. **Never modify files without `--fix`**: Default mode is report-only. Respect the user's working tree.\n2. **Use the project's own config**: Do not invent lint rules. Use whatever config files exist in the project.\n3. **Use the project's installed version**: Always prefer `npx`, `cargo`, or the project-local binary. Do not use globally installed tools unless no local version exists.\n4. **Handle missing tools gracefully**: If a config file exists but the tool is not installed, inform the user and provide the install command (e.g., `npm install --save-dev eslint`).\n5. **Respect `.gitignore` and ignore patterns**: Do not lint `node_modules`, `dist`, `build`, `target`, `.git`, or other commonly ignored directories. Most tools handle this automatically; verify they do.\n6. **Limit output**: If there are more than 50 issues, show the first 30 grouped by severity, then summarize the rest with counts per file. Do not flood the user with hundreds of lines.\n7. **Exit cleanly**: After presenting results, do not take further action. Let the user decide next steps.\n\n\u003C\u002Fcritical_rules>\n",{"name":5,"description":7},"main","e62d23e713a36a0570f7f5c3ee69868b1131e548","src\u002Fresources\u002Fskills\u002Flint","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli","https:\u002F\u002Fgithub.com\u002Fcmetech","https:\u002F\u002Fwww.cmetech.io","Corey Ellis is a seasoned data engineer with over 20 years of experience in the field. He is the founder of CME Technologies LLC.","2026-06-17 22:50:56",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add cmetech\u002Fotto-cli --skill lint",{"tool":38,"command":39},"bunx","bunx skills add cmetech\u002Fotto-cli --skill lint",{"tool":41,"command":42},"pnpm","pnpm dlx skills add cmetech\u002Fotto-cli --skill lint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Flint\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M74PWE6AVSD8RDS1M3Q6TH95","write-milestone-brief","Synthesize the current conversation into a milestone brief (PRD). Writes to `M###-CONTEXT.md` by default, or files a GitHub issue only with explicit user confirmation. Use when asked to \"turn this into a PRD\", \"draft a milestone brief\", \"capture this context\", \"write it up\", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-milestone-brief\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M74PWB6CEEQPGS9HRQY4QQPZ","write-docs","Collaborative document authoring workflow for proposals, technical specs, decision docs, README sections, ADRs, and long-form prose that must work for fresh readers. Use when asked to \"write the docs\", \"draft a proposal\", \"write a spec\", \"write an RFC\", \"write the README\", or when a document needs to be understandable by someone without this session's context. Three stages: gather context, iterate on structure, reader-test for a stranger.","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fwrite-docs\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74PW7SJQ8H516MDBQ7WV1BN","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74PW5JAA6D34Z8QBN1HQ014","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74PW1YP2Y03GMDYD443BVHQ","verify-before-complete","Block completion claims until verification evidence has been produced in the current message. Use before marking a task\u002Fslice\u002Fmilestone complete, before creating a commit or PR, before saying \"it works\" or \"tests pass\", and any time you are about to claim work is done. The rule is: evidence before claims, always — running the verification must happen now, not \"earlier in the session\". Fresh output or no claim.","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fverify-before-complete\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74PVXR5GE8HE55YWEG7ENBP","userinterface-wiki","UI\u002FUX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.","https:\u002F\u002Fgithub.com\u002Fcmetech\u002Fotto-cli\u002Fblob\u002Fmain\u002Fsrc\u002Fresources\u002Fskills\u002Fuserinterface-wiki\u002FSKILL.md",[],[]]