QLTY During Development
Run QLTY checks during code writing to catch issues early.
Run QLTY after significant code changes:
# Quick lint check
qlty check
# Format code
qlty fmt
# Check specific files
qlty check src/sdk/providers.ts
# Auto-fix issues
qlty check --fix
After writing code:
qlty check on changed filesqlty fmt to ensure formattingnpx skills add parcadei/qlty-during-development下载完整 Skill 目录,包含 SKILL.md 及所有相关文件
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Capture and automate macOS UI with the Peekaboo CLI.
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
Category:developer