ci-pipeline-synthesizer
CI Pipeline Synthesizer
Generate a CI config that actually runs, by reading the repo rather than asking the user twenty questions.
Step 1 — Detect the build
Read the repo, not the user's description. Signals:
| File present | Ecosystem | Build command | Test command |
|---|---|---|---|
package.json |
Node/JS | npm ci then npm run build |
npm test |
pyproject.toml / setup.py |
Python | pip install -e . or uv sync |
pytest / python -m pytest |
Cargo.toml |
Rust | cargo build --release |
cargo test |
go.mod |
Go | go build ./... |
go test ./... |
pom.xml |
Java/Maven | mvn -B package |
mvn -B test |
build.gradle / build.gradle.kts |
Java/Gradle | ./gradlew build |
./gradlew test |
Makefile (and nothing else) |
Make | make |
make test (if target exists) |
Dockerfile (and no build system) |
Container-only | docker build . |
— (look for test stage) |
More from santosomar/general-secure-coding-agent-skills
code-review-assistant
Performs structured code review on a diff or file set, producing inline comments with severity levels and a summary. Checks correctness, error handling, security, and maintainability — in that priority order. Use when reviewing a pull request, when the user asks for a code review, when preparing code for merge, or when a second opinion is needed on a change.
15dependency-resolver
Diagnoses and resolves package dependency conflicts — version mismatches, diamond dependencies, cycles — across npm, pip, Maven, Cargo, and similar ecosystems. Use when install fails with a resolution error, when two packages require incompatible versions of a third, or when upgrading one dependency breaks another.
4configuration-generator
Generates configuration files for services and tools (app config, logging config, linter config, database config) from a brief description of desired behavior, matching the target format's idioms. Use when bootstrapping a new service, when the user asks for a config file for a specific tool, or when translating config intent between formats.
3api-design-assistant
Reviews and designs API contracts — function signatures, REST endpoints, library interfaces — for usability, evolvability, and the principle of least surprise. Use when designing a new public interface, when reviewing an API PR, when the user asks whether a signature is well-designed, or when planning a breaking change.
2code-refactoring-assistant
Executes refactorings — extract method, inline, rename, move — in small, behavior-preserving steps with a test between each. Use when the user wants to restructure working code, when cleaning up after a feature lands, or when a smell has been identified and needs fixing.
2code-smell-detector
Identifies code smells — structural patterns that correlate with maintainability problems — and explains why each matters in context. Use when reviewing a PR for structural quality, when the user asks what's wrong with a piece of code that isn't buggy, or when prioritizing refactoring targets.
2