ci-loop
Runs CI tests locally to rapidly identify and fix code failures.
Install
mkdir -p .claude/skills/ci-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14737" && unzip -o skill.zip -d .claude/skills/ci-loop && rm skill.zipInstalls to .claude/skills/ci-loop
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run the full CI pipeline locally and iterate until all tests pass.Key capabilities
- →Run server tests using Gradle.
- →Run shared module tests (JVM/server) using Gradle.
- →Run Android tests using Gradle.
- →Parse test failures to extract class, method, error, and stack trace.
- →Apply fixes iteratively for failing tests.
- →Re-run specific tests after applying fixes.
How it works
This skill automates the local CI loop by running various test suites (server, shared, Android), parsing any failures to identify the source, applying fixes iteratively, and re-running specific tests until all tests pass. It concludes with a final verification step.
Inputs & outputs
When to use ci-loop
- →Run CI locally
- →Debug failed tests
- →Verify fix iteration
About this skill
CI Loop Skill
Run the full CI pipeline locally and iterate until all tests pass.
Trigger
Use this skill when:
- Starting work on a feature or bugfix
- Before creating a commit or PR
- When asked to "run tests" or "make sure everything passes"
- After making changes to verify they work
Workflow
1. Initial Assessment
# Check current state
./gradlew assemble --dry-run
2. Run Full Test Suite
# Server tests
./gradlew :server:test --info
# Shared module tests (JVM/server)
./gradlew :shared:serverTest --info
# Android tests
./gradlew :clients:android:app:testDebugUnitTest --info
3. Parse Failures
For each failure in the output:
- Extract the test class and method name
- Extract the error message and stack trace
- Identify the source file and line number
4. Fix Loop
while failures exist:
for each failure:
1. Read the failing test file
2. Read the source file under test
3. Analyze the failure using failure-patterns.json
4. Apply the fix
5. Re-run the specific test:
./gradlew :module:test --tests "FullyQualifiedTestClass.testMethod"
6. If still failing, try alternative fix
7. If fixed, move to next failure
5. Final Verification
# Run full suite to catch regressions
./gradlew check
# If all pass, report success
# If new failures, add to queue and continue
Quick Commands
# Run specific test
./gradlew :server:test --tests "dev.hyo.deepline.server.routes.UserRoutesTest.testCreateUser"
# Run tests with stacktrace
./gradlew :server:test --stacktrace
# Continue after failure
./gradlew :server:test --continue
Success Criteria
- All tests pass (exit code 0)
- No compilation errors
- Security validation passes (see security-scan skill)
When not to use it
- →When the project does not use Gradle.
- →When not working on a feature or bugfix.
- →When all tests already pass.
Limitations
- →The skill is designed for Gradle-based projects.
- →It relies on specific Gradle commands for different test suites.
- →Security validation is mentioned but not detailed within this skill's scope.
How it compares
This skill provides an automated, iterative workflow for debugging and fixing failing tests locally, simplify the process of achieving a passing CI pipeline compared to manual debugging.
Compared to similar skills
ci-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ci-loop (this skill) | 0 | 4mo | Review | Intermediate |
| springboot-verification | 4 | 4mo | Review | Intermediate |
| code-checklist | 0 | 4mo | Review | Beginner |
| semoss-testing-ci | 0 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by hyodotdev
View all by hyodotdev →You might also like
springboot-verification
affaan-m
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
code-checklist
comeredon
Critical code requirements checklist derived from actual build failures. Use before committing code or when troubleshooting compilation errors.
semoss-testing-ci
SEMOSS
Use when the user wants to add JUnit/Mockito tests for Java reactors, set up pre-commit hooks (husky + the pre-commit framework), or wire GitHub Actions CI (lint + unit-test workflows) to a SEMOSS app. The base template ships none of this to stay lean — this skill carries the full, working setup as
verification-loop
Patrick-Rex
Stratum 变更验证闭环技能。用于在提交前对受影响模块、架构边界、文档同步与安全基线做一次可执行检查。
mvnf
eclipse-rdf4j
Run Maven tests in this repo with a consistent workflow (module test-artifact cleanup, root -Pquick install to refresh .m2_repo, then module verify or a single test class/method). Use when asked to run tests/verify in the rdf4j multi-module build or when the user says mvnf.
analyze-failures
saleor
Analyze Playwright E2E test failure reports from CI. Parses merged blob reports, groups similar errors, and delegates to specialized subagents for investigation and fixes. Use when CI tests fail or when asked to fix E2E test failures.