ci-cd-pipeline

ci-cd-pipeline is a skill for Claude Code, Codex from fideguch/my_pm_tools. It costs 0 tokens per session (2,270 once invoked), scanned A, original, MIT.

A setup guide for GitHub Actions, GitHub's built-in automation service, that runs code-quality checks when changes are proposed or merged.

In plain words
What is it for?
Use it to create or update a CI pipeline for projects using tools such as Node.js, Python, Go, or Rust.
Why use it?
It automates checks such as linting, type checking, tests, and builds so broken changes are caught before they are merged.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create or update a CI pipeline for projects using tools such as Node.js, Python, Go, or Rust.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fideguch/my_pm_tools/ci-cd-pipeline
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fideguch/my_pm_tools --skill ci-cd-pipeline
Clone the repo
git clone --depth 1 https://github.com/fideguch/my_pm_tools

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ci-cd-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/fideguch/my_pm_tools/ci-cd-pipeline/github.svg)](https://agentmods.dev/skills/fideguch/my_pm_tools/ci-cd-pipeline)
Your own site
<a href="https://agentmods.dev/skills/fideguch/my_pm_tools/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/fideguch/my_pm_tools/ci-cd-pipeline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ci-cd-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/fideguch/my_pm_tools/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/fideguch/my_pm_tools/ci-cd-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02270
Opus 5 $0.00000 $0.01135
Sonnet 5 $0.00000 $0.00454
Haiku 4.5 $0.00000 $0.00227

Measured 9d ago against content hash bfe315ee7314, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ci-cd-pipeline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/ci-cd-pipeline/SKILL.md · 316 lines

How it starts

The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Actions CI/CD 品質パイプライン構築スキル

メタデータ

  • トリガー: 「CI/CDを設定したい」「GitHub Actions パイプライン」「品質チェック自動化」「CI設定」
  • 前提条件: GitHub リポジトリ、package.json または pyproject.toml が存在

概要

GitHub Actions を使った品質パイプラインを構築するスキル。 PR 作成・更新時に lint → typecheck → test → build の品質ゲートを自動実行し、 マージ品質を担保する。


Phase 1: プロジェクト分析

1.1 技術スタック検出

# パッケージマネージャー判定
[ -f pnpm-lock.yaml ] && echo "pnpm" || \
[ -f yarn.lock ] && echo "yarn" || \
[ -f bun.lockb ] && echo "bun" || \
echo "npm"

# ランタイム判定
[ -f package.json ] && echo "Node.js"
[ -f pyproject.toml ] && echo "Python"
[ -f go.mod ] && echo "Go"
[ -f Cargo.toml ] && echo "Rust"

# Node.js バージョン確認
[ -f .nvmrc ] && cat .nvmrc
[ -f .node-version ] && cat .node-version
node -v 2>/dev/null

1.2 既存スクリプト確認

# package.json のスクリプト一覧
node -e "const p=require('./package.json'); console.log(Object.keys(p.scripts||{}).join('\n'))"

1.3 既存ワークフロー確認

ls -la .github/workflows/ 2>/dev/null

Phase 2: CI ワークフロー生成

2.1 基本品質チェック(.github/workflows/ci.yml

name: CI Quality Check

on:
  pull_request:
    branches: [main, develop]
  push:
    branches: [main]

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

jobs:
  quality:
    runs-on: ubuntu-latest
    timeout-minutes: 15
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'

      - name: Install dependencies
        run: |
          if [ -f package-lock.json ]; then
            npm ci
          else
            npm install
          fi

      - name: Lint
        run: npm run lint --if-present

      - name: Type Check
        run: npm run typecheck --if-present

      - name: Format Check
        run: npm run format:check --if-present

      - name: Unit Tests
        run: |
          TEST_SCRIPT=$(node -e "const p=require('./package.json'); console.log(p.scripts?.test || '')")
          if [ -n "$TEST_SCRIPT" ] && [ "$TEST_SCRIPT" != "echo \"Error: no test specified\" && exit 1" ]; then
            npm test -- --coverage --passWithNoTests
          else
            echo "No test script configured, skipping"
          fi

      - name: Build
        run: npm run build --if-present

Read the full file on GitHub · 316 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 316 lines · 0 tokens per session scan A bfe315ee7314

Subscribe to this mod's changes

ci-cd-pipeline is a skill published in the GitHub repository fideguch/my_pm_tools (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,270 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

flutter-mcp-toolkit-repo-maintainer

Maintain mcpflutter releases, CHANGELOG, version pins, docs, and CI. Use when cutting a release, editing CHANGELOG.md, bumping VERSION, running release-please, sync-skills, check-contracts, or updating install/docs for npx skills and flutter-mcp-toolkit init.

Arenukvern/mcp_flutter · 71 tokens

servicenow-cicd-devops

ServiceNow release-engineering surface — CI/CD app install/scan/rollback, DevOps change-control & artifact registration, update-set create/preview/commit/back-out, source-control apply/import, plugin activate/rollback, and ATF test-suite runs via the servicenow-api MCP server. Use when the agent must deploy or roll…

Knuckles-Team/servicenow-api · 185 tokens

swarm-release

Full SwarmAI release cycle: preflight checks, version bump, binary build, desktop package, smoke test, and GitHub publish. The single release path — handles version bump + tag plus build/package/smoke stages. TRIGGER: "release", "cut release", "ship it", "发版". NOT FOR: sswarm-build, shive-manager use cases.

xg-gh-25/SwarmAI · 85 tokens

swarm-ci

Check SwarmAI GitHub Actions CI status: list recent runs, diagnose failures, and summarize health. Replaces ad-hoc gh run commands with structured output. TRIGGER: "CI status", "check CI", "is CI green", "CI failures". NOT FOR: pytest use cases.

xg-gh-25/SwarmAI · 66 tokens

orchardcore-docker

Skill for containerizing Orchard Core with Docker. Covers Dockerfile creation with multi-stage builds, dockerignore configuration, docker-compose setup for multiple database providers, HTTPS deployment in containers, environment-specific targeting, image optimization, and CI/CD considerations. Use this skill when…

CrestApps/CrestApps.AgentSkills · 168 tokens

blazemeter-integrations

Comprehensive guide for BlazeMeter Integrations, including APM tools, CI/CD pipelines, and development tools. Use when working with integrations for (1) Integrating APM tools (AppDynamics, Datadog, New Relic, CloudWatch, DX APM, Dynatrace, Delphix), (2) Integrating CI/CD tools (Jenkins, GitHub Actions, GitLab CI/CD…

Blazemeter/bzm-mcp · 131 tokens