skills.rest
Hashzin-0
Hashzin-0COMMUNITY
Explore all skills by this author →
GitHub

build-assist

Run npm builds and extract TypeScript, ESLint, and framework errors.

Updated Mar 12, 2026
Search Tags:#typescript#npm#build#nextjs#ci#fixes#error-parsing
One-click install
npx skills add https://github.com/Hashzin-0/Curion --skill build-assist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-assist
Source: https://github.com/Hashzin-0/Curion/tree/main/.opencode/skills/build-assist
Command: npx skills add https://github.com/Hashzin-0/Curion --skill build-assist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify and resolve npm build failures by running the project's build command, parsing compiler and linter output, and presenting actionable error details so fixes can be applied one at a time with human approval.

Core Features & Use Cases

  • Run and capture build output: Executes npm run build in the project root and collects the full stdout/stderr.
  • Structured error parsing: Extracts file paths, line numbers, and raw error messages from TypeScript, ESLint, Next.js, and generic build outputs using common patterns.
  • Guided, safe fixes: Presents one error at a time, asks for confirmation before editing, applies a targeted fix, and re-runs the build to verify results, with a configurable maximum of five rounds.
  • Use Cases: Local developer debugging, CI triage for failing builds, and helping contributors reproduce and fix build errors during code reviews.

Quick Start

Run build-assist to execute npm run build, parse detected errors, and propose the first fix for your approval.

Frequently Asked Questions about build-assist

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

FAQPage Schema
How do I fix npm build failures in a Next.js TypeScript project?▼

Fix npm build failures by executing the build to capture output, parsing compiler and linter errors to extract file paths and line numbers, and proposing targeted fixes one by one with user confirmation before re-running the build to verify.

What is the best way to parse TypeScript compilation errors during local development?▼

Parsing TypeScript compilation errors involves executing the build, extracting structured error details like file path and line number from raw output, and presenting them individually for guided fixing and subsequent build re-validation.

Can I use build-assist to triage failing CI builds for Node applications?▼

Yes, you can use this approach to triage failing CI builds for Node applications by running the build, detecting TypeScript and framework build failures, and extracting actionable error details for contributors to reproduce and resolve.

Does this guided fix process modify my project files automatically without approval?▼

No, the guided fix process requests user confirmation before modifying any files, ensuring safe application of targeted fixes to resolve parsed build errors, and then re-runs the build to validate the results.

What are the limitations when re-running builds to validate error fixes?▼

A limitation when re-running builds to validate error fixes is a configurable maximum round limit of five iterations, restricting the number of sequential automated build validations applied during the error resolution process.

Related Skills

Explore More Software Engineering Skills→
while-basicwhile-basic

test/failing-test

Execute a Node tool that intentionally fails to expose stdout and stderr.

Community
Basic
nomos-guildnomos-guild
4

cgov-build

Run Next.js builds and triage TypeScript errors into actionable to-dos.

Official
Intermediate
futureteafuturetea

ESLint Setup

Configure ESLint for JavaScript and TypeScript projects with flat or legacy configs.

Community
Intermediate
xxihxxih
1

typescript-circular-dependency

Detect circular import dependencies in TypeScript and JavaScript projects.

Community
Intermediate