sow

Automate oxlint, oxfmt, and Knip integration for TypeScript projects.

6|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/markacianfrani/armor --skill sow-markacianfrani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sow
Source: https://github.com/markacianfrani/armor/tree/main/skills/sow
Command: npx skills add https://github.com/markacianfrani/armor --skill sow-markacianfrani

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oxlint, oxfmt, typescript, @j178/prek, knip, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill eliminates the friction of configuring new TypeScript projects by automating the installation and setup of high-performance linting, formatting, and dependency hygiene tools.

Core Features & Use Cases

  • Tooling Scaffolding: Automatically installs and configures oxlint, oxfmt, and Knip to ensure consistent code quality and dependency health.
  • Project Hygiene: Enforces strict TypeScript configurations and manages git hooks via prek to prevent regressions.
  • Use Case: When starting a new repository, use this skill to instantly apply a standardized, high-performance development environment that includes linting, formatting, and dead-code detection without manual configuration.

Quick Start

Use the sow skill to initialize the current directory as a new TypeScript project with standard linting and formatting.

Frequently Asked Questions about sow

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

FAQPage Schema
How do I set up a new TypeScript project with oxlint and Knip?

You can standardize a TypeScript project setup by automating the integration of oxlint for linting, oxfmt for formatting, and Knip for dependency management, applying strict code quality guardrails without manual configuration.

What is the best way to standardize linting and formatting in an existing TypeScript repository?

Standardizing linting and formatting in an existing TypeScript repository is best achieved by automating the integration of high-performance tools like oxlint and oxfmt, which enforce consistent code quality and project hygiene across the codebase.

Does this TypeScript tooling setup include automated git hooks?

Yes, the setup includes automated git hooks managed via prek to prevent regressions by enforcing strict TypeScript configurations and running checks before commits are finalized.

Can I use this scaffolding for dead-code detection in TypeScript projects?

Yes, you can use this scaffolding for dead-code detection because it integrates Knip, a tool designed to analyze project-graph hygiene and identify unused dependencies and dead code within TypeScript environments.

What are the limitations of using oxlint for TypeScript static analysis?

A limitation of using oxlint for TypeScript static analysis is that it focuses on high-performance linting and formatting, meaning it specifically targets code quality and dependency guardrails rather than runtime type checking or execution logic.