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.mdsource 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
- Parse CI configuration files (
).github/workflows/*.yml - Apply detection rules by category (Performance, Security, Maintenance, Reliability)
- Calculate impact per antipattern (time cost, risk level)
- Generate prioritized fix recommendations
Detection Rules
| ID | Antipattern | Detection | Category |
|---|---|---|---|
| PERF-001 | Sequential jobs | on independent jobs | Performance |
| PERF-002 | No caching | Missing | Performance |
| PERF-003 | Duplicate installs | Multiple | Performance |
| SEC-001 | Secrets in logs | | Security |
| SEC-002 | Mutable actions | | Security |
| SEC-003 | No permissions | Missing | Security |
| SEC-004 | Unsafe PR target | + untrusted checkout | Security |
| MAINT-001 | Duplicated config | Similar job definitions | Maintenance |
| MAINT-002 | Hardcoded values | Repeated version strings | Maintenance |
| MAINT-003 | No workflow reuse | Identical steps across workflows | Maintenance |
| REL-001 | No timeouts | Missing | Reliability |
| REL-002 | No health checks | Services without | Reliability |
| REL-003 | No retry | Network ops without retry logic | Reliability |
Severity Classification
| Category | Severity |
|---|---|
| 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:
- Parse configuration
- Apply detection rules
- Calculate impact
- Generate prioritized fixes
References
— detailed antipattern examples with problematic and fixed YAML configurations for all categories (Performance, Security, Maintenance, Reliability)references/patterns.md