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
- ZeroTokenClaw/agents-skillsedited, first seen Sep 21, 2026
- matarpeles/skills-registry-demoedited, first seen May 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- ZeroTokenClaw/agents-skills★ 199% same
- matarpeles/skills-registry-demo★ 099% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository85 other files it gives its agents.
- accessibility-auditingSkill
- adding-analyticsSkill
- adding-api-docsSkill
- adding-authSkill
- adding-dockerSkill
- adding-e2e-testsSkill
- adding-error-trackingSkill
- adding-feature-flagsSkill
- adding-stripeSkill
- api-smoke-testingSkill
- architecture-decision-recordsSkill
- auditing-performanceSkill
- auditing-securitySkill
- auto-type-checkingSkill
- babysitting-prSkill
- best-of-n-solvingSkill
- building-skills-from-patternsSkill
- cavemanSkill
- codebase-onboardingSkill
- comparing-branches-visuallySkill
- converting-css-modules-to-tailwindSkill
- converting-css-to-tailwindSkill
- creating-prSkill
- dark-mode-testingSkill
- database-designSkill
- design-an-interfaceSkill
- detecting-port-conflictsSkill
- domain-modelSkill
- edit-articleSkill
- exporting-to-pngSkill
- finding-dev-server-urlSkill
- fixing-broken-linksSkill
- form-testingSkill
- generating-imagesSkill
- git-guardrails-claude-codeSkill
- github-triageSkill
- grill-meSkill
- grinding-until-passSkill
- improve-codebase-architectureSkill
- incident-responseSkill
- kubernetes-deployingSkill
- migrate-to-shoehornSkill
- monitoring-terminal-errorsSkill
- network-request-auditingSkill
- obsidian-vaultSkill
- parallel-ci-triageSkill
- parallel-code-reviewSkill
- parallel-exploringSkill
- parallel-test-fixingSkill
- profiling-performanceSkill
- prompt-engineeringSkill
- python-tdd-with-uvSkill
- qaSkill
- react-native-patternsSkill
- recording-browser-flow-as-testSkill
- request-refactor-planSkill
- responsive-testingSkill
- reviewing-codeSkill
- saving-workspace-contextSkill
- scaffold-exercisesSkill
- The first 60 shown.
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
- Very specific: line 21
Look for commands like npm run build, pnpm build, turbo build, docker build, tsc, vite build.
- Distinctive: line 25
Read the terminal file periodically.
- Distinctive: line 47
When an error appears:
- Distinctive: line 49
Read and fix the source file
- Distinctive: line 50
If the build supports watch mode, it will re-trigger automatically
- Distinctive: line 51
If not, note the fix and let the build continue — it may reveal more errors
- Very specific: line 55
After the build completes (check for exit_code in terminal footer):
- Distinctive: line 69
Don't fix warnings during the build — collect them and address after
≈ “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.
Files
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>/*.txtLook 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 TSModule not found/Cannot find moduleSyntaxError/TypeErrorFailed to compile
Warnings (collect for summary):
WARNING/Warning:/warnDeprecation/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:
- Extract the file path and line number from the error
- Read and fix the source file
- If the build supports watch mode, it will re-trigger automatically
- 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
--noEmitis useful for type-checking without a full build
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
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.

