code-quality
Code Quality
Run comprehensive code quality checks: TypeScript typecheck, ESLint linting, Prettier formatting, and Markdown validation.
Scripts
Scripts are embedded in skills/code-quality/scripts/finalize.sh. Agents execute:
bash skills/code-quality/scripts/finalize.sh agent- Auto-fixes formatting issues (agent mode)bash skills/code-quality/scripts/finalize.sh ci- Read-only checks for CI pipelines (no auto-fixes)
Checks Performed
- TypeScript Type Checking - Validates type safety
- ESLint Linting - Checks code style and potential issues
- Prettier Formatting - Ensures consistent code formatting
- Markdown Quality - Validates markdown files (trailing whitespace, missing newlines)
Workflow
Running Quality Checks
-
Choose mode:
- Agent mode: Execute
bash skills/code-quality/scripts/finalize.sh agent- Auto-fixes formatting issues while checking for type and lint errors - CI mode: Execute
bash skills/code-quality/scripts/finalize.sh ci- Read-only checks suitable for CI pipelines (no auto-fixes)
- Agent mode: Execute
-
Review results: Check terminal output for errors and warnings
- TypeScript errors show file paths and line numbers
- ESLint warnings include rule names and suggestions
- Prettier issues are auto-fixed in agent mode
- Markdown issues show file paths and line numbers
-
Fix issues: Address any errors that weren't auto-fixed
- Type errors: Fix type mismatches, missing types, or incorrect imports
- Lint errors: Follow ESLint suggestions or disable rules with comments if needed
- Markdown issues: Fix trailing whitespace or add missing newlines
-
Re-run checks: Execute the same command again to verify all issues are resolved
- Script exits with code 0 if all checks pass
- Script exits with code 1 if any check fails (useful for CI pipelines)
Integration with Other Skills
- Run after code-review skill to ensure reviewed code meets quality standards
- Run before docs-check skill to ensure code is clean before documentation review
- Use in CI pipelines as a quality gate before merging PRs
Examples
When agents use this skill, they execute:
# Agent mode (auto-fixes)
bash skills/code-quality/scripts/finalize.sh agent
# CI mode (read-only)
bash skills/code-quality/scripts/finalize.sh ci
Integration
- Run after code-review skill to ensure reviewed code meets quality standards
- Run before docs-check skill to ensure code is clean before documentation review
- Use in CI pipelines as a quality gate before merging PRs
References
references/documentation-guide.md- Documentation standards
Output
Terminal output. Exits with code 0 (pass) or 1 (fail) for CI pipelines.
More from lukasstrickler/ai-dev-atelier
ui-animation
Guide tasteful UI animation with easing, springs, layout animations, gestures, and accessibility. Covers Tailwind and Motion patterns. Use when: (1) Implementing enter/exit animations, (2) Choosing easing curves, (3) Configuring springs, (4) Layout animations and shared elements, (5) Drag/swipe gestures, (6) Micro-interactions, (7) Ensuring prefers-reduced-motion accessibility. Triggers: animate, animation, easing, spring, transition, motion, layout, gesture, drag, swipe, reduced motion, framer motion.
31use-graphite
Manage stacked PRs with Graphite CLI (gt) instead of git push/gh pr create. Auto-detects Graphite repos and blocks conflicting commands with helpful alternatives. Use when: (1) About to run git push or gh pr create in a Graphite repo, (2) Creating a new branch for a feature, (3) Submitting code for review, (4) Large changes that should be split into reviewable chunks, (5) Hook blocks your git command and suggests gt equivalent. NOT for: repos not initialized with Graphite, git add/commit/status/log. Triggers: git push blocked, gh pr create blocked, create branch, submit PR, stacked PRs, split large PR, gt create, gt submit, graphite workflow.
14tdd
Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests.
9git-commit
Write clear git commits with Conventional Commits format. Detects project conventions from history and config. Guides commit granularity. Use when: (1) Completing working code, (2) Code builds and tests pass, (3) Ready to save, (4) Before pushing, (5) After review feedback. Triggers: automatically when finishing commitable work that builds and passes tests.
8image-generation
Generate, edit, and upscale AI images. Use when creating visual assets for apps, websites, or documentation. FREE Cloudflare tier for iterate generation (~96/day), Fal.ai for paid tiers. Four quality tiers (iterate/default/premium/max). Supports text specialists, multi-ref editing, SVG, background removal. Triggers: generate image, create image, edit image, upscale, logo, picture of, remove background.
7docs-write
Write or update documentation (tutorial, how-to, reference, explanation) with clear style, structure, visuals, API/ADR/runbook patterns. Use when: (1) Creating or updating docs after code changes, (2) During PR preparation or addressing review feedback, (3) Adding new features that need documentation, (4) Updating API endpoints, database schemas, or configuration, (5) Creating ADRs or runbooks, (6) Adding or updating diagrams and visual documentation, (7) When documentation needs to be written or revised, (8) For tutorial creation, how-to guides, or technical writing, or (9) For documentation standards compliance and structure. Triggers: write docs, update documentation, create documentation, write tutorial, document API, write ADR, create runbook, add documentation, document this, write how-to.
7