setup-cicd

Generates a GitHub Actions pipeline that validates and publishes an AI toolkit package to AWS CodeArtifact via OIDC.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Assamir/ai-toolkit --skill setup-cicd-assamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-cicd
Source: https://github.com/Assamir/ai-toolkit/tree/main/.cursor/skills/setup-cicd
Command: npx skills add https://github.com/Assamir/ai-toolkit --skill setup-cicd-assamir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a secure CI/CD pipeline to publish an npm package to AWS CodeArtifact from GitHub Actions requires careful OIDC configuration, workflow permissions, and validation logic that is easy to get wrong. This Skill generates the complete workflow file without relying on long-lived AWS access keys. ## Core Features & Use Cases - Workflow Generation: Creates .github/workflows/ci.yml with OIDC-based AWS authentication using aws-actions/configure-aws-credentials@v4 and id-token: write permissions. - Package Validation: Adds a validation job that checks pack.yaml fields, verifies every skills/*/SKILL.md has matching name and description frontmatter, and runs npm pack --dry-run. - Secure Publishing: Adds a publish job restricted to pushes on the default branch that runs aws codeartifact login and publishes from the package directory. - Use Case: A team maintaining an AI toolkit monorepo needs to publish their package to a private CodeArtifact repository on every merge to main, without storing AWS credentials in GitHub secrets. ## 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 via OIDC using aws-actions/configure-aws-credentials@v4, then run aws codeartifact login to authenticate npm, and publish from the package directory. The publish job should only trigger on pushes to the default branch.

How to authenticate GitHub Actions with AWS without access keys?

Use OIDC federation 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 eliminates the need for long-lived AWS_ACCESS_KEY_ID or AWS_SECRET_ACCESS_KEY credentials.

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. The token is exchanged for temporary AWS credentials through the assumed IAM role.

Why should the publish job not run on pull requests?

Running publish on pull requests would allow unreviewed code to reach the package registry and expose OIDC credentials to untrusted fork code. Restrict publishing to pushes on the default branch only.

What validation should run before publishing an npm package in CI?

Validate that pack.yaml exists with required fields, confirm every skills directory has SKILL.md files with name and description frontmatter matching the directory name, and run npm pack --dry-run to verify the package builds correctly.