Files
GLM-Tools-Skills-Agents/skills/community/dyad/lint/SKILL.md
uroma b60638f0a3 Add community skills, agents, system prompts from 22+ sources
Community Skills (32):
- jat: jat-start, jat-verify, jat-complete
- pi-mono: codex-cli, codex-5.3-prompting, interactive-shell
- picoclaw: github, weather, tmux, summarize, skill-creator
- dyad: 18 skills (swarm-to-plan, multi-pr-review, fix-issue, lint, etc.)
- dexter: dcf valuation skill

Agents (23):
- pi-mono subagents: scout, planner, reviewer, worker
- toad: 19 agent configs (Claude, Codex, Gemini, Copilot, OpenCode, etc.)

System Prompts (91):
- Anthropic: 15 Claude prompts (opus-4.6, code, cowork, etc.)
- OpenAI: 49 GPT prompts (gpt-5 series, o3, o4-mini, tools)
- Google: 13 Gemini prompts (2.5-pro, 3-pro, workspace, cli)
- xAI: 5 Grok prompts
- Other: 9 misc prompts (Notion, Raycast, Warp, Kagi, etc.)

Hooks (9):
- JAT hooks for session management, signal tracking, activity logging

Prompts (6):
- pi-mono templates for PR review, issue analysis, changelog audit

Sources analyzed: jat, ralph-desktop, toad, pi-mono, cmux, pi-interactive-shell,
craft-agents-oss, dexter, picoclaw, dyad, system_prompts_leaks, Prometheus,
zed, clawdbot, OS-Copilot, and more
2026-02-13 10:58:17 +00:00

1.5 KiB

name, description
name description
dyad:lint Run pre-commit checks including formatting, linting, and type-checking, and fix any errors.

Lint

Run pre-commit checks including formatting, linting, and type-checking, and fix any errors.

Instructions

  1. Run formatting check and fix:

    npm run fmt
    

    This will automatically fix any formatting issues.

  2. Run linting with auto-fix:

    npm run lint:fix
    

    This will fix any auto-fixable lint errors.

  3. Fix remaining lint errors manually:

    If there are lint errors that could not be auto-fixed, read the affected files and fix the errors manually. Common issues include:

    • Unused variables or imports (remove them)
    • Missing return types (add them)
    • Any other ESLint rule violations
  4. Run type-checking:

    npm run ts
    
  5. Fix any type errors:

    If there are type errors, read the affected files and fix them. Common issues include:

    • Type mismatches (correct the types)
    • Missing type annotations (add them)
    • Null/undefined handling issues (add appropriate checks)
  6. Re-run all checks to verify:

    After making manual fixes, re-run the checks to ensure everything passes:

    npm run fmt && npm run lint && npm run ts
    
  7. Summarize the results:

    • Report which checks passed
    • List any fixes that were made manually
    • If any errors could not be fixed, explain why and ask the user for guidance
    • If all checks pass, confirm the code is ready to commit