circleci-builds

Savant verdict: Analyzed

Scanned or evaluated by Savant; not yet both passing.

Live evaluation

0 pass · 1 investigate · 8 fail across 9 cases. Jev accepted 9 of 12 LLM-drafted cases. Drafted and run by nvidia/nemotron-3-super-120b-a12b, validated and scored by jev-latest.

• Our CircleCI pipeline on the main branch is failing at the 'run-tests' step in the 'build' job. The error shows 'npm ERR! code ERESOLVE Unable to resolve dependency tree' when trying to install dependencies. The commit SHA is a1b2c3d4e5f6. Can you help diagnose and fix this?positive case · fail
• The CircleCI workflow for our Python service is failing consistently in the 'deploy' job at the 'aws s3 sync' step with 'botocore.exceptions.NoCredentialsError'. We're on feature/auth-update branch, commit SHA 9f8e7d6c5b4a. The AWS keys are configured in project settings but the job fails every time.positive case · fail
• Our Node.js monorepo pipeline fails in the 'lint' step of the 'test' job with 'ESLint: Failed to load plugin @typescript-eslint declared in '.eslintrc.js': Cannot find module '@typescript-eslint/eslint-plugin''. This happens on every commit to develop branch, latest SHA is d4c3b2a1f0e9. The package is in devDependencies but seems missing during install.positive case · fail
• Can you write a new CircleCI config from scratch for our Go microservice that uses Docker layers caching and runs tests with race detection?negative case · fail
• Our monitoring shows high CPU usage in CircleCI jobs. Can you help us optimize resource allocation to reduce costs?negative case · fail
• Our CircleCI pipeline that deploys to production is failing with 'Permission denied' when trying to run 'kubectl apply'. We suspect the IAM role for the CircleCI runner might be misconfigured, but we don't have access to audit logs. Fixing this could break production if done wrong.escalation case · fail
• Our CircleCI pipeline on the feature/login branch fails in the 'test' job at the 'pytest' step with 'ModuleNotFoundError: No module named 'requests''. The same commit passes locally when we run pytest. What should we do?edge case · investigate
• The CircleCI pipeline for our Java application fails in the 'build' job at the 'mvn compile' step with 'Failed to read artifact descriptor for org.apache.commons:commons-lang3:jar:3.12.0'. The error happens about 30% of the time on reruns of the same commit. We use the Maven Docker image and cache ~/.m2. What should we do?edge case · fail

Safety (NVIDIA SkillSpector)

0 patterns found

Structure

• No license declaredConfirm you may reuse this skill before importing it into your repository.

SKILL.md

---
name: circleci-builds
description: Diagnose and fix failing CircleCI builds quickly and safely. Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines, identify root causes from logs, and implement minimal fixes in configuration, test setup, or build-related code paths.
---

# CircleCI Builds

## Overview

Use this skill to turn failing CircleCI pipelines into actionable fixes with clear evidence. Prioritize fast root-cause isolation, minimal safe patches, and explicit validation criteria.

Read `references/transient-vs-deterministic.md` when deciding whether a failure should be fixed in code/config, retried, mitigated with rerun behavior, or reported as external/transient.
Read `../config/references/test-results-and-splitting.md` when the failure involves missing test metadata, flaky test reruns, test splitting, or JUnit XML setup.

## Inputs To Gather

- Failing pipeline/workflow/job identifier
- Branch and commit SHA
- First failing step and key log lines
- Whether rerun on same commit reproduces failure

## Workflow

1. Identify the primary failing signal.
   - Record the first failing job and step, not every downstream failure.
2. Classify issue type.
   - Config syntax/reference issue
   - Environment/toolchain mismatch
   - Dependency/cache issue
   - Test or build regression
   - External/transient failure
3. Apply the smallest viable fix.
   - Patch only files tied to confirmed root cause.
   - Keep workaround scope narrow.
4. Validate.
   - Run highest-signal local checks when possible.
   - Define expected CircleCI success signals for the rerun.
5. Report residual risk.
   - Call out unverified assumptions and likely follow-up checks.

## Guardrails

- Do not hide deterministic failures with blanket retries.
- Avoid mixing unrelated refactors into incident fixes.
- Treat external service outages as report-and-mitigate unless user asks for deeper redesign.
- Keep confidence levels explicit when logs are incomplete.
- Do not recommend automatic reruns or flaky-test workflows until the failure is classified as plausibly transient.

## Output Contract

Provide:

1. Failure summary (pipeline/workflow/job/step).
2. Root-cause hypothesis with confidence.
3. Applied changes with file list.
4. Validation plan and expected pass signal.
5. Remaining risk.