skills.rest
a2f0
a2f0COMMUNITY
Explore all skills by this author →
GitHub

fix-tests

Diagnoses and fixes failing CI jobs by analyzing logs and categorizing errors.

Updated Aug 23, 2026
Search Tags:#code quality#automation#testing#debugging#troubleshooting#ci
One-click install
npx skills add https://github.com/a2f0/tearleads --skill fix-tests-a2f0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-tests
Source: https://github.com/a2f0/tearleads/tree/main/.codex/skills/fix-tests
Command: npx skills add https://github.com/a2f0/tearleads --skill fix-tests-a2f0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the diagnosis and resolution of failing Continuous Integration (CI) jobs, ensuring code quality and smooth deployment pipelines.

Core Features & Use Cases

  • Automated Failure Diagnosis: Identifies specific failing CI jobs and analyzes their logs.
  • Log Analysis & Categorization: Differentiates between lint errors, test failures, coverage drops, and infrastructure issues.
  • Targeted Fixes: Provides job-specific guidance for resolving common problems in build, E2E, and mobile release pipelines.
  • Use Case: When your CI pipeline fails, invoke this Skill to pinpoint the exact cause, whether it's a flaky E2E test or a build-time linting error, and receive actionable steps to fix it.

Quick Start

Use the fix-tests skill to diagnose and fix the failing electron-e2e CI job.

Frequently Asked Questions about fix-tests

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

FAQPage Schema
How do I diagnose and fix failing CI jobs automatically?▼

To diagnose and fix failing CI jobs automatically, this Skill analyzes commit statuses, downloads logs and artifacts, and categorizes failures to provide specific remediation steps for build, E2E, and mobile release pipelines.

How do I troubleshoot CI pipeline failures caused by flaky E2E tests or coverage drops?▼

Troubleshooting CI pipeline failures from flaky E2E tests or coverage drops is handled by categorizing log errors and providing targeted fixes for build, E2E, and mobile release jobs.

Can I target a specific failing CI job for fixing instead of the whole pipeline?▼

Yes, you can target a specific failing CI job for fixing, such as the electron-e2e job, and receive automated verification through local execution commands and Git integration.

What types of CI failures can be categorized and resolved?▼

CI failures that can be categorized and resolved include lint errors, test failures, coverage drops, and infrastructure issues across build, E2E, and mobile release jobs.

How do I verify CI fixes locally before pushing changes?▼

You can verify CI fixes locally before pushing changes by using the Skill's automated local execution commands and Git integration to apply and validate the remediation steps.

Related Skills

Explore More Software Engineering Skills→
YuriNakayamaYuriNakayama

E2E Fix

Diagnose and fix failing Playwright E2E tests in GitHub Actions CI.

Community
Advanced
hamzaPixlhamzaPixl
2

runbook

Investigate production incidents and create runbooks using Bash and Grep.

Community
Advanced
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
LordKuperLordKuper

test-flakiness

Detects flaky tests by aggregating CI logs and analyzing pass/fail patterns across runs.

Community
Advanced