kcenon/ci-debugging
plugin/skills/ci-debugging/SKILL.md
Diagnose and fix CI/CD pipeline failures: GitHub Actions errors, build failures, test timeouts, TLS/auth issues, platform-specific failures, dependency resolution problems, and deployment errors. Use when CI checks fail, builds break, tests timeout, or pipeline errors need systematic root-cause analysis and resolution.
$ install --global
skillsauthnpx skillsauth add kcenon/claude-config ci-debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 10:42 AM8.4s2 files scanned
SKILL.md
- name:
- ci-debugging
- description:
- Diagnose and fix CI/CD pipeline failures: GitHub Actions errors, build failures, test timeouts, TLS/auth issues, platform-specific failures, dependency resolution problems, and deployment errors. Use when CI checks fail, builds break, tests timeout, or pipeline errors need systematic root-cause analysis and resolution.
- allowed-tools:
- Bash, Read, Grep, Glob, WebFetch
- model:
- sonnet
- context:
- fork
- argument-hint:
- <run-id-or-url>
- paths:
- .github/workflows/**, Makefile, CMakeLists.txt
- when_to_use:
- CI failure, build error, test timeout
CI/CD Debugging Skill
When to Use
- CI build failures
- GitHub Actions workflow errors
- TLS certificate or authentication issues
- Platform-specific compilation failures
- Dependency resolution problems
Diagnostic Flow
Step 1: Categorize Failure Type
Determine which category the failure falls into:
| Category | Indicators | Priority | |----------|------------|----------| | Environment/Auth | TLS errors, token expired, permission denied | Check first | | Platform-Specific | Works on Linux fails on Windows, vice versa | Check second | | Missing Dependencies | Module not found, package missing | Check third | | Actual Code Bug | Test assertions, logic errors | Check last |
Step 2: Environment/Auth Issues
Check for sandboxed environment limitations:
# Test GitHub API connectivity
curl -s --connect-timeout 5 https://api.github.com/zen
# Check GitHub CLI auth status
gh auth status
# Verify GITHUB_TOKEN
echo "Token present: ${GITHUB_TOKEN:+yes}"
Common Issues:
- TLS certificate errors -> Try diagnosis with connectivity check first
- Token expired -> Re-authenticate with
gh auth login - Sandbox blocked -> Use local git operations as fallback
Step 3: Platform-Specific Issues
Look for platform-specific patterns:
# Search for Unix-specific code
grep -rn "MSG_DONTWAIT\|/dev/null\|fork()" src/
# Check for Windows path issues
grep -rn '"/tmp\|"/var' src/
Fallback: Add conditional compilation or use cross-platform alternatives.
Step 4: Dependency Issues
# Check for missing packages (Node.js)
npm ls 2>&1 | grep "MISSING" || echo "No missing npm packages"
# For Python
pip check 2>&1 || echo "No pip issues"
# For CMake/C++
cmake --build build/ 2>&1 | grep -i "error\|not found" || echo "Build OK"
Step 5: Code Bug Analysis
If none of the above:
- Read the failing test output carefully
- Identify the assertion that failed
- Trace back to the implementation
- Fix the actual bug
Fallback Strategies
GitHub API Blocked
Priority order:
1. Use gh CLI (preferred)
2. Direct curl with GITHUB_TOKEN
3. Local git operations only
4. Manual intervention required
TLS/Certificate Issues
Priority order:
1. Check system certificates
2. Verify proxy settings
3. Use alternative connectivity check
4. Report as environment issue
Quick Commands
| Issue | Command |
|-------|---------|
| Check CI logs | gh run view --log-failed |
| Re-run failed | gh run rerun --failed |
| View workflow | gh run view |
| Check auth | gh auth status |
| List failed runs | gh run list --status failure |
Reference Documents (Import Syntax)
@./reference/common-failures.md
Related Skills
kcenon/security-audit
testing
VerifiedTrustedCommunity
Comprehensive security audit covering OWASP Top 10, input validation, authentication, authorization, secret management, dependency vulnerabilities, and injection attack prevention. Use when reviewing security posture, implementing auth flows, handling user input, auditing dependencies, conducting penetration test prep, or before production deployment.
2SKILL.mdUpdated Apr 16, 2026
kcenon/project-workflow
development
VerifiedTrustedCommunity
Provides workflow guidelines for problem-solving, git commits, GitHub issues, PRs, build management, and testing. Use when planning tasks, creating issues, submitting PRs, managing builds, or writing tests.
2SKILL.mdUpdated Apr 16, 2026
kcenon/pr-review
development
VerifiedTrustedCommunity
Review pull requests with comprehensive analysis covering code quality, security vulnerabilities, performance implications, test coverage, documentation completeness, and architectural impact. Use when reviewing PRs, conducting code reviews, evaluating merge readiness, or assessing change impact across the codebase.
2SKILL.mdUpdated Apr 16, 2026
kcenon/performance-review
development
VerifiedTrustedCommunity
Performance optimization analysis: CPU/memory profiling, caching strategies, database query optimization, connection pooling, concurrency patterns, memory leak detection, and throughput improvement. Use when code is slow, memory usage is high, latency needs reduction, or conducting performance reviews before release.
2SKILL.mdUpdated Apr 16, 2026