菜单
Run pnpm format then pnpm lint from the repo root and fix issues until both pass. Use after edits, when CI is red on lint/format, or before opening a PR. Keywords: pnpm, format, lint, trunk, monorepo, code style.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/yu-iskw/github-secops-agent --skill lint-fix命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | lint-fix |
| description | Run pnpm format then pnpm lint from the repo root and fix issues until both pass. Use after edits, when CI is red on lint/format, or before opening a PR. Keywords: pnpm, format, lint, trunk, monorepo, code style. |
Working directory: Repository root (directory that contains the root package.json).
Run in order:
pnpm format
pnpm lint
On failure: Read command output (stdout and stderr). Fix the underlying source or config. Then repeat from step 2 — run both pnpm format and pnpm lint again so Trunk formatting and checks stay aligned.
Iteration cap: After 5 full cycles (format + lint), if either command still fails, stop and summarize remaining errors and files; do not loop indefinitely.
Success: The last pnpm format and the last pnpm lint both exit with code 0.
The default commands match root package.json (format → trunk fmt, lint → trunk check -y). If the user explicitly needs repo-wide variants, use pnpm format:all or pnpm lint:all instead — only when they ask for that scope.