mcpField
T
tailing-build-output

tailing-build-output

github.com/spencerpaulyDevelopment868391 installsUpdated 13w ago
Repository

About tailing-build-output

A skill for monitoring build output through terminal files, addressing errors while a build runs, and reporting the final status and warnings. It is intended for coding agents working on builds.

Key features

  1. 01Poll terminal files for build output
  2. 02Identify errors, warnings, and progress
  3. 03Fix source issues during a build
  4. 04Summarize status and remaining warnings

Use cases

  1. 01Monitor a running build for failures
  2. 02Resolve errors as they appear
  3. 03Review build warnings after completion

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill tailing-build-output

After installing, type/tailing-build-outputin Claude Code to confirm it loaded.

Details

From the project README

Tailing Build Output

Watch a build process in real time via terminal files and fix issues as they appear.

Workflow

1. Start or Find the Build

Either start the build yourself or find the terminal running it:

head -n 10 <terminals_folder>/*.txt

Look for commands like npm run build, pnpm build, turbo build, docker build, tsc, vite build.

2. Poll for Output

Read the terminal file periodically. Look for:

Errors (fix immediately):

  • ERROR / Error: / error TS
  • Module not found / Cannot find module
  • SyntaxError / TypeError
  • Failed to compile

Warnings (collect for summary):

  • WARNING / Warning: / warn
  • Deprecation / deprecated
  • Unused imports/variables
  • Large bundle size warnings (asset size limit)

Progress indicators:

  • Webpack: [XX%], modules, chunks
  • Turbo: task completion logs
  • Docker: Step X/Y
  • TypeScript: file count
3. Fix Errors in Flight

When an error appears:

  1. Extract the file path and line number from the error
  2. Read and fix the source file
  3. If the build supports watch mode, it will re-trigger automatically
  4. If not, note the fix and let the build continue — it may reveal more errors
4. Summary Report

After the build completes (check for exit_code in terminal footer):

Build Summary:
  Status: Failed (exit code 1) / Succeeded
  Duration: ~45s
  Errors fixed: 3
  Remaining warnings: 2
    - Large bundle: src/pages/Dashboard.tsx (450kb)
    - Deprecated API: useRouter from 'next/router'

Tips

  • Don't fix warnings during the build — collect them and address after
  • For turbo build, errors may appear in parallel task output — check all task logs
  • Docker builds cache layers — if you fix a file early in the Dockerfile, later layers rerun
  • TypeScript's --noEmit is useful for type-checking without a full build

Comments

Markdown supported