deno-expert

Guide Deno code reviews and debugging with expert best practices.

91|8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/denoland/skills --skill deno-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deno-expert
Source: https://github.com/denoland/skills/tree/main/skills/deno-expert
Command: npx skills add https://github.com/denoland/skills --skill deno-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert-level guidance and checklists for Deno code reviews and debugging, ensuring adherence to best practices and faster issue resolution.

Core Features & Use Cases

  • Expert guidance on Deno runtime, Fresh island architecture, and package selection to inform code reviews.
  • Code review checklists for imports, configuration, and tooling, with concrete examples.
  • Use cases include reviewing Deno/Fresh projects, debugging runtime issues, and evaluating deployment readiness.

Quick Start

Provide a concise expert review for a given Deno code snippet by describing recommended changes and the rationale in a single action-oriented request.

Frequently Asked Questions about deno-expert

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

FAQPage Schema
How do I perform a Deno code review to ensure import hygiene and proper configuration?

Debug Deno runtime issues by leveraging built-in tooling like deno fmt, deno lint, deno test, and deno doc. Applying codified expert best practices helps evaluate packages and resolve complex runtime issues across deployments.

What is the best way to review Fresh island architecture in a Deno project?

Yes, you can use deno lint and deno test to evaluate deployment readiness. Expert guidance applies these built-in Deno tools alongside configuration checks to debug complex runtime issues and enforce best practices across deployments.

Why should I use jsr instead of deno.land/x when reviewing Deno imports?

Deno code review checklists cover imports, configuration, and tooling with concrete examples. They enforce proper deno.json setup and leverage built-in tools to guide high-quality reviews and faster debugging.

Does this guidance apply to debugging complex Deno deployment issues?

Before debugging Deno, configure a proper deno.json file and establish import hygiene using jsr. This setup enables built-in tools like deno lint and deno test to function correctly during expert code reviews.