skills.rest
open-hax
open-haxOFFICIAL
Explore all skills by this author →
GitHub

workspace-lint

Lint affected TypeScript and Markdown files across workspace submodules.

6|Updated Mar 11, 2026
Search Tags:#typescript#markdown#workspace#pnpm#code-quality#lint#nx
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill workspace-lint-open-hax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace-lint
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/workspace-lint
Command: npx skills add https://github.com/open-hax/opencode-skills --skill workspace-lint-open-hax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint all TypeScript and Markdown files across the entire workspace, including all submodules under orgs/**, to catch style and correctness issues early and reduce review iterations.

Core Features & Use Cases

  • Lint affected workspace files via Nx detection, with a full-run fallback available.
  • Script uses scripts/nx-affected.mjs to collect uncommitted changes and run nx affected --target=lint.
  • Provides concise results with file paths and line numbers for violations; ideal before commits or PRs in multi-repo workspaces.

Quick Start

Invoke the workspace-lint skill to lint all affected files across the workspace and its submodules.

Frequently Asked Questions about workspace-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint TypeScript and Markdown files across an entire workspace?▼

Lint TypeScript and Markdown files across an entire workspace by using Nx detection to target affected projects via pnpm lint, or run pnpm lint:all for a full workspace scan. This catches style and correctness issues early across all submodules.

What is the best way to lint affected projects in a pnpm multi-repo workspace?▼

Lint affected projects in a pnpm multi-repo workspace by using Nx affected detection. A custom script collects uncommitted changes to run nx affected --target=lint, ensuring code quality before commits or PRs.

Does workspace linting support submodules under orgs directories?▼

Yes, workspace linting supports submodules under orgs/** directories. It applies ESM modules and strict TypeScript practices to scan all submodules, reducing review iterations by catching violations early.

How do I get lint results with file paths and line numbers for multi-repo PRs?▼

Get lint results with file paths and line numbers for multi-repo PRs by running the workspace lint process. It provides concise outputs detailing exact violation locations across the workspace and its submodules.

Can I enforce strict TypeScript and ESM module practices during workspace linting?▼

Yes, you can enforce strict TypeScript and ESM module practices during workspace linting. The process applies these strict configurations across all affected projects and submodules to ensure consistency.

Related Skills

Explore More Software Engineering Skills→
Montte-erpMontte-erp
6

nx-plugins

Discover and install Nx plugins to extend an Nx workspace.

Official
Basic
getsentrygetsentry
246

sentry-code-review

Parse Sentry comments in GitHub PRs and generate targeted fixes.

Official
Advanced
open-haxopen-hax
6

workspace-typecheck

Enforce strict TypeScript checks across workspace projects using Nx affected detection.

Official
Intermediate
ehtbantonehtbanton

lint-staged-config-generator

Generate lint-staged configuration files for multiple languages and linters.

Community
Basic