Menu
Lint and format the codebase, then fix the issues found. Use when asked to lint, format, clean up style, or resolve linter/formatter errors.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Rank the functions/modules changed this session by test-worthiness and output TEST / integration-only / SKIP per symbol. Uses graphify blast-radius when graphify-out/ exists, a static rubric otherwise. Use when you changed several units and are unsure which deserve a unit test, or before writing tests for a batch of new code.
Use when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.
Use when publishing a new version of gitai to npm — cutting a release, bumping the version, shipping to the registry — or when a release was cut but the new version never reached npm, or a user reports the CLI still showing an old version.
Use when asked to generate, build, prepare, optimize or assemble a /goal command for autonomous or overnight execution — triggers: "montar goal", "gerar goal autônomo", "preparar task overnight", "goal para sessão autônoma", "otimizar goal", "goal builder".
Smoke test end-to-end do gitai CLI em repo temporário
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
| name | lint-fix |
| description | Lint and format the codebase, then fix the issues found. Use when asked to lint, format, clean up style, or resolve linter/formatter errors. |
CLAUDE.md (or .claude/rules/).Keep changes minimal and scoped to the lint/format issues; do not refactor unrelated code.