skills.rest
Tehminanaz
TehminanazCOMMUNITY
Explore all skills by this author →
GitHub

ci-cd-troubleshooting

Diagnose CI/CD pipeline failures and linting blockers in full-stack projects.

1|Updated Dec 4, 2025
Search Tags:#linting#troubleshooting#build#eslint#github-actions#ci-cd#workflows
One-click install
npx skills add https://github.com/Tehminanaz/Evolution-of-Todo --skill ci-cd-troubleshooting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-cd-troubleshooting
Source: https://github.com/Tehminanaz/Evolution-of-Todo/tree/main/.claude/skills/ci-cd-troubleshooting
Command: npx skills add https://github.com/Tehminanaz/Evolution-of-Todo --skill ci-cd-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a systematic approach to resolving common CI/CD failures, frontend build conflicts, and linting blockers in modern full-stack projects.

Core Features & Use Cases

  • Frontend build stabilization: Diagnose and fix build failures caused by module resolution, ESLint config mismatches, and bundler errors.
  • Linting and code quality: Aligns tooling versions and configurations to prevent blockers in CI.
  • CI workflow improvements: Establish deterministic steps and tooling recommendations for GitHub Actions, Trivy, and build caches.

Quick Start

Run a structured triage to identify and fix the most common CI/CD failure modes.

Frequently Asked Questions about ci-cd-troubleshooting

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

FAQPage Schema
How do I fix CI/CD build failures caused by ESLint config mismatches?▼

To fix CI/CD build failures from ESLint config mismatches, align tooling versions and configurations across your environment to prevent linting blockers. This process systematically resolves frontend build conflicts and module resolution errors.

What is the best way to troubleshoot GitHub Actions workflows when a build fails?▼

The best way to troubleshoot GitHub Actions workflows is to run a structured triage applying step-by-step checks for build failures. This establishes deterministic CI workflow steps and recommends specific tooling versions to stabilize pipelines.

How does module resolution affect frontend build stabilization in CI pipelines?▼

Module resolution affects frontend build stabilization by causing bundler errors and build failures during CI pipelines. Diagnosing these resolution issues ensures full-stack integration works correctly and prevents unexpected pipeline blockers.

Can I use this CI/CD troubleshooting approach for both frontend and backend integration issues?▼

Yes, you can use this CI/CD troubleshooting approach for frontend and backend integration issues in modern full-stack projects. It diagnoses build failures, linting blockers, and infrastructure problems across the entire pipeline.

Why does my CI pipeline fail even after updating my bundler and build tooling?▼

CI pipelines often fail after updating bundler and build tooling due to lingering configuration mismatches or non-deterministic steps. Establishing deterministic workflows and aligning tooling versions systematically resolves these blockers.

Related Skills

Explore More Software Engineering Skills→
mashharukimashharuki

repo-documentation

Generate README-style documentation from repository files and directory structure.

Community
Intermediate
barrydobsonbarrydobson

github-actions

Automate secure CI/CD pipelines with GitHub Actions workflows.

Community
Intermediate
sambersamber
2.9k

golang-lint

Configure and run golangci-lint to analyze Go projects and interpret results.

Community
Advanced
martin-hsu-testmartin-hsu-test
1

canary

Monitor a URL for 10 minutes post-deploy to detect console errors, latency regressions, and page failures.

Community
Advanced