Agent skill · software engineering · sickn33
newman-cicd-integration
Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.
Why this skill is useful
Generates specific CI/CD configurations for running Newman that are tailored to various platforms, which the AI wouldn't reliably create on its own.
What it needs
Requires node installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Newman CI/CD Integration Generator When to Use Use this skill when you need generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing. Use this skill whenever the user wants to run Newman in a CI pipeline, integrate Postman collections into automated builds, set up API tests in GitHub Actions, GitLab CI, Jenkins,... Generate complete, copy-paste-ready CI/CD pipeline configs that install Newman and run Postman collections as part of automated builds. --- What to Collect From the User Before generating a config, determine: 1. CI platform — GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, Bitbucket? 2. Collection source — local file in repo, or Postman API URL? 3. Environment — local env file in repo, or env vars injected by CI secrets? 4. Reporters needed — JUnit XML (for CI test results panel), HTML report, or both? 5. Node.js version preference (default: 18) 6. Trigger — on every push, pull request, schedule, or after deploy? 7. Fail build on test failure? — almost always yes; confirm --- Platform Templates GitHub Actions --- GitLab CI --- Jenkins (Declarative Pipeline) --- Azure DevOps --- CircleCI --- Best Practices Secrets — never hardcode credentials Always inject sensitive values as CI environment variables/secrets: GitHub: Settings > Secrets and Variables > Actions GitLab: Settings > CI/CD > Variables Jenkins: Manage Jenkins > Credentials Azure DevOps: Pipelines > Variables Reference in Newman via --env-var "KEY=$SECRETNAME" or pre-set in the environment file. Store collection and environment files in the repo Add results/ to .gitignore. Always use if: always() / when: always Ensure test result artifacts are published even when Newman exits with a failure code. Exit codes Newman exits with code 1 if any tests fail — this automatically fails the pipeline step. Use --bail if you want to stop on the first failure rather than running all tests. --- How to Generate Configs 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/newman-cicd-integration