Cursor Skill

tailing-build-output

Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Summarize issues and fix them before the build finishes.

LLM Mart · 0 points · 23 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download spencerpauly-awesome-cursor-skills-resources_tailing-build-output-99cd265.zip · 1 KB
Part of spencerpauly/awesome-cursor-skills — 65 skills

Install

skills CLI npx skills add https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install spencerpauly-awesome-cursor-skills@llmmart
Git git clone https://github.com/spencerpauly/awesome-cursor-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole spencerpauly/awesome-cursor-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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
Files (awesome-cursor-skills)
  • SKILL.md 2.1 KB
    ---
    name: tailing-build-output
    description: Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Summarize issues and fix them before the build finishes.
    user-invocable: true
    ---
    
    # 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:
    
    ```bash
    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 (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related