jsr-audit

Audit JavaScript/TypeScript packages for JSR readiness and compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jahanson/cc-plugins --skill jsr-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jsr-audit
Source: https://github.com/jahanson/cc-plugins/tree/main/jsr-audit/skills/jsr-audit
Command: npx skills add https://github.com/jahanson/cc-plugins --skill jsr-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive guidance and tooling to audit JavaScript/TypeScript packages for JSR readiness, ensuring compliance before publishing.

Core Features & Use Cases

  • Validates required metadata and exports configuration (deno.json/jsr.json).
  • Checks module/documentation coverage and symbol documentation to improve discoverability and reliability.
  • Provides a structured audit process and report template to prepare for publishing with provenance.

Quick Start

Run the audit process on a project to verify JSR readiness and generate an actionable report.

Frequently Asked Questions about jsr-audit

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

FAQPage Schema
How do I check if my package is ready for JSR publishing?

A JSR readiness audit validates your package's deno.json or jsr.json metadata, exports mapping, and module documentation coverage. It generates an actionable report to identify compliance gaps and detect slow types before you publish.

What does a JSR compliance audit include for TypeScript packages?

A JSR compliance audit includes validating required metadata, exports mapping correctness, and module documentation coverage. It checks for explicit imports, proper @module tags, symbol documentation, and detects slow types during a dry-run.

How do I run a JSR dry-run to detect slow types?

Run a JSR dry-run audit to detect slow types and verify provenance requirements. The audit examines your package's exports configuration and module documentation, ensuring all symbols are properly documented before the actual publishing step.

Why does my JSR package need @module tags in documentation?

JSR requires @module tags in documentation to improve package discoverability and reliability. The audit checks module documentation and symbol coverage, ensuring your package meets JSR's documentation compliance standards before publishing.

Can I use a JSR audit for JavaScript packages without TypeScript?

Yes, the JSR audit applies to both JavaScript and TypeScript packages targeted for JSR publishing. It validates the deno.json or jsr.json configuration, exports mapping, and documentation coverage regardless of the underlying source language.