setup-cicd

Generates a GitHub Actions pipeline that validates and publishes packages to AWS CodeArtifact via OIDC.

Updated May 20, 2026
One-click install
npx skills add https://github.com/ZawilecxD/trAInR --skill setup-cicd-zawilecxd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-cicd
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/setup-cicd
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill setup-cicd-zawilecxd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a secure CI/CD pipeline to publish an AI toolkit package to AWS CodeArtifact requires careful handling of OIDC authentication, workflow permissions, and validation steps, which is error-prone when done manually. ## Core Features & Use Cases - Workflow Generation: Creates .github/workflows/ci.yml with a validation job and a publish job gated to the default branch. - OIDC-Based AWS Authentication: Configures aws-actions/configure-aws-credentials@v4 with id-token: write so no long-lived AWS access keys are needed. - Package Validation: Checks pack.yaml fields, verifies every skills/*/SKILL.md has matching name and description frontmatter, and runs npm pack --dry-run. - Use Case: A team maintaining an AI toolkit monorepo needs every merge to main to automatically validate skill metadata and publish the package to their CodeArtifact repository without storing AWS secrets in GitHub. ## Quick Start Ask the assistant to run the setup-cicd skill to generate the GitHub Actions workflow that validates and publishes the ai-toolkit package to AWS CodeArtifact using OIDC.

Frequently Asked Questions about setup-cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish an npm package to AWS CodeArtifact from GitHub Actions?

Create a workflow that configures AWS credentials with aws-actions/configure-aws-credentials@v4, runs aws codeartifact login to authenticate npm, then publishes from the package directory. The publish job should run only on pushes to the default branch.

How to authenticate GitHub Actions to AWS without access keys?

Use OIDC by adding id-token: write to workflow permissions and configuring aws-actions/configure-aws-credentials@v4 with a role ARN stored in GitHub secrets. This avoids long-lived AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY credentials entirely.

What permissions does a GitHub Actions workflow need for AWS OIDC?

The workflow needs contents: read to check out code and id-token: write to request an OIDC token from GitHub. That token is exchanged for temporary AWS credentials through the configured IAM role.

Can I publish to CodeArtifact on pull requests?

No, publishing should be restricted to pushes on the default branch only. Pull requests should run the validation job, which checks pack.yaml fields, SKILL.md frontmatter, and npm pack --dry-run, without publishing.

Why does CodeArtifact publish fail in GitHub Actions?

Common causes include a missing or incorrect AWS role ARN secret, absent id-token: write permission, or skipping the aws codeartifact login step. Verify the IAM role trust policy allows the GitHub OIDC provider and the target repository.