菜单
Runs the appropriate linter and formatter for specified files in react-gts-app. Maps file extensions to GTS-backed tools (eslint, prettier) and reports remaining errors. Use when linting a specific file or directory, or after editing code before moving on.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prepares a git commit for react-gts-app by analyzing staged changes and detecting commit style from the repo's signals — user history, recent repo history, commit templates, and any commit-msg hook. Confirms with the user only when signals conflict. Use when the user wants to commit changes or asks to prepare a commit message.
Studies existing code patterns, architecture, and conventions in react-gts-app. Reads reference components and tests to extract naming, import order, RTL query priority, and GTS-enforced conventions before writing new code. Use when writing new code or entering an unfamiliar area.
Generates a production-ready AGENTS.md and complete .claude/ setup through guided codebase discovery and targeted interview. Detects the user's global setup, the project's filesystem, and installed tooling — then asks the user to confirm rather than assuming. Creates skills, hooks, settings, and symlinks tailored to the project. Use when setting up a new project for AI-assisted development or updating an existing setup.
Implements a new feature in react-gts-app using a dialogue-first workflow: researches the codebase, asks one clarifying question at a time, explores 2–3 approaches with trade-offs, validates the chosen design section-by-section, then implements after approval. Use when implementing new functionality or a significant change.
Guides collaborative dialogue to turn ideas into designs through one-at-a-time questions, approach exploration with trade-offs, and incremental validation. Does not implement code. Use before creative work or significant changes — when the user asks to "brainstorm", "think through", "explore options for", or similar.
Handles user confusion by explaining actual behavior and determining whether there is a real issue to address. Primary goal is clarification, not a fix. Use when the user says "I don't understand", "this doesn't make sense", "why does this do X", or shows contradictory expectations about existing code.
| name | lint |
| description | Runs the appropriate linter and formatter for specified files in react-gts-app. Maps file extensions to GTS-backed tools (eslint, prettier) and reports remaining errors. Use when linting a specific file or directory, or after editing code before moving on. |
| user-invocable | true |
| disable-model-invocation | true |
| argument-hint | <file or directory> |
Run the right tool for each file type against the GTS-backed toolchain in example/.
$ARGUMENTS is a file, lint that file.$ARGUMENTS is a directory, lint every supported file under it.$ARGUMENTS is empty, lint the working-tree changes: cd example && git diff --name-only HEAD.Run all commands from inside example/ so local gts / eslint / prettier resolutions work:
| Extension | Commands |
|---|---|
.ts, .tsx, .js, .jsx | npx eslint --fix <file> then npx prettier --write <file> |
.css, .scss | npx prettier --write <file> |
.json, .md, .yaml, .yml | npx prettier --write <file> |
| anything else | skip — do not invent a tool |
Example invocation for a TS file:
cd example && npx eslint --fix src/App.tsx && npx prettier --write src/App.tsx
After --fix passes, re-run npx eslint <file> on TS/JS files to surface anything that couldn't be auto-fixed. For CSS/JSON/MD, a successful prettier --write is the report.
Summarize:
When the user asks to lint everything, prefer npm run fix (auto-fix) or npm run lint (report-only) inside example/ rather than walking files one at a time. They dispatch through GTS exactly as this skill does.
cd example before running tools — the linters rely on the local config and node_modules.