agentleFS
witi-projectswiti-projects/Skills/tailing-build-output/SKILL.md

tailing-build-output

Skill2 starsChanged 7 months agoMITView on GitHub

Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Summarize issues and fix them before the build finishes. Use when the user says "/tailing-build-output", "tailing build output", or asks about tailing build output.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 21
  2. Distinctive:

    Read the terminal file periodically.

    line 25
  3. Distinctive:

    When an error appears:

    line 47
  4. Distinctive:

    Read and fix the source file

    line 49
  5. Distinctive:

    If the build supports watch mode, it will re-trigger automatically

    line 50
  6. Distinctive:

    If not, note the fix and let the build continue — it may reveal more errors

    line 51
  7. Very specific:

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

    line 55
  8. Distinctive:

    Don't fix warnings during the build — collect them and address after

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.