Awesome-claude-code detect-ci-antipatterns

Detects CI/CD antipatterns in pipeline configurations. Identifies slow pipelines, security issues, maintenance problems, and provides remediation guidance.

install
source · Clone the upstream repo
git clone https://github.com/dykyi-roman/awesome-claude-code
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/dykyi-roman/awesome-claude-code "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/detect-ci-antipatterns" ~/.claude/skills/dykyi-roman-awesome-claude-code-detect-ci-antipatterns && rm -rf "$T"
manifest: skills/detect-ci-antipatterns/SKILL.md
source content

CI Antipattern Detector

Detects common CI/CD antipatterns and provides remediation guidance.

When to Use

  • Reviewing GitHub Actions workflow files
  • Auditing CI pipeline performance (slow builds)
  • Checking CI security configuration
  • Reducing pipeline maintenance burden
  • Improving build reliability

Analysis Approach

  1. Parse CI configuration files (
    .github/workflows/*.yml
    )
  2. Apply detection rules by category (Performance, Security, Maintenance, Reliability)
  3. Calculate impact per antipattern (time cost, risk level)
  4. Generate prioritized fix recommendations

Detection Rules

IDAntipatternDetectionCategory
PERF-001Sequential jobs
needs
on independent jobs
Performance
PERF-002No cachingMissing
actions/cache
Performance
PERF-003Duplicate installsMultiple
composer install
Performance
SEC-001Secrets in logs
echo.*secrets\.
Security
SEC-002Mutable actions
uses:.*@(main|master|v\d)$
Security
SEC-003No permissionsMissing
permissions:
Security
SEC-004Unsafe PR target
pull_request_target
+ untrusted checkout
Security
MAINT-001Duplicated configSimilar job definitionsMaintenance
MAINT-002Hardcoded valuesRepeated version stringsMaintenance
MAINT-003No workflow reuseIdentical steps across workflowsMaintenance
REL-001No timeoutsMissing
timeout-minutes
Reliability
REL-002No health checksServices without
options:
Reliability
REL-003No retryNetwork ops without retry logicReliability

Severity Classification

CategorySeverity
Security (SEC-*)Critical
Performance (PERF-*)Major
Reliability (REL-*)Major
Maintenance (MAINT-*)Minor

Output Format

# CI Antipattern Analysis

**File:** `.github/workflows/ci.yml`
**Total Antipatterns:** N

## Summary by Category

| Category | Count | Impact |
|----------|-------|--------|
| Performance | N | +X min/build |
| Security | N | Risk level |
| Maintenance | N | Technical debt |
| Reliability | N | Flaky builds |

## Detected Antipatterns

### [ID]: [Title]
**Severity:** Critical/Major/Minor
**Impact:** [Specific impact]
**Location:** Lines X-Y

**Current:**
[Problematic configuration]

**Fix:**
[Corrected configuration]

## Estimated Improvements

| Metric | Before | After | Improvement |
|--------|--------|-------|-------------|
| Build time | X min | Y min | -Z% |
| Security score | C | A | +N grades |

## Remediation Priority

1. **Immediate:** Security issues
2. **This sprint:** Performance issues
3. **Next sprint:** Maintenance issues

Usage

Provide:

  • Path to CI configuration
  • Specific categories to focus on (optional)

The detector will:

  1. Parse configuration
  2. Apply detection rules
  3. Calculate impact
  4. Generate prioritized fixes

References

  • references/patterns.md
    — detailed antipattern examples with problematic and fixed YAML configurations for all categories (Performance, Security, Maintenance, Reliability)