How do I install the Managing Github CI skill?

Run npx get-skill add tomevault-io/managing-github-ci in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Managing Github CI safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Managing Github CI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Managing Github CI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Managing Github CI?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Managing Github CI by tomevault-io — Agent Skill

Name: Managing Github CI
Author: tomevault-io

Managing Github CI

Configures GitHub Actions workflows and CI/CD pipelines. Use when creating workflow YAML, managing npm releases, troubleshooting CI failures, configuring Husky hooks, or setting up release automation. Do NOT use for local development commands or application code.

tomevault-io Updated Sep 17, 2026

File contents

GitHub CI Automation

Overview

Guide the configuration and management of GitHub Actions workflows, release automation, and CI/CD pipelines for the Saleor Configurator project.

When to Use

Creating or modifying GitHub Actions workflows
Setting up automated releases via Changesets
Troubleshooting CI failures
Configuring pre-commit/pre-push hooks (Husky)

Quick Reference

Workflow	Trigger	Purpose
`test-on-pr.yml`	PR to main	Typecheck, lint, test, build
`release.yml`	Push to main	Changesets publish to npm
`changeset-bot.yml`	PR opened/synced	Comment on missing changesets

Project CI Architecture

.github/
├── workflows/
│   ├── test-on-pr.yml      # PR validation
│   ├── release.yml         # Automated releases
│   └── changeset-bot.yml   # Changeset automation

.husky/
├── pre-push               # Schema docs generation

.changeset/
├── config.json            # Changeset configuration
└── *.md                   # Pending changesets

Workflows

test-on-pr.yml

Validates PRs before merge. Runs: typecheck, lint, test, build. Uses pnpm 9 + Node 20.

See references/workflow-templates.md for full YAML.

Required Checks

Check	Command	Purpose
Type check	`pnpm typecheck`	TypeScript validation
Lint	`pnpm lint`	Biome linting
Test	`pnpm test`	Vitest test suite
Build	`pnpm build`	Compilation check

release.yml

Automated npm releases via Changesets. Triggers on push to main with concurrency control.

Uses changesets/action@v1 with pnpm publish:ci-prod. Requires GITHUB_TOKEN and NPM_TOKEN.

Release Flow

1. Developer creates changeset -> pnpm changeset
2. PR merged to main
3. Changesets action runs:
   a. If changesets exist -> Creates "Version Packages" PR
   b. If version PR merged -> Publishes to npm

changeset-bot.yml

Comments on PRs about missing changesets. Uses changesets/bot@v1.

Pre-Push Hooks (Husky)

Located in .husky/pre-push:

Runs pnpm generate-schema-docs before every push
Auto-commits schema documentation updates
Ensures docs stay in sync with schema changes

Changesets Configuration

Located in .changeset/config.json. Key settings: access: "public", baseBranch: "main".

Type	When to Use
`patch`	Bug fixes, documentation, refactoring
`minor`	New features, non-breaking enhancements
`major`	Breaking changes, API modifications

GitHub CLI

Use gh for workflow management: gh run list, gh run view <id>, gh run watch <id>, gh run rerun <id>, gh pr checks <number>.

Troubleshooting CI Failures

Reproduce Locally

Failure	Command
Type check	`pnpm typecheck` or `npx tsc --noEmit`
Lint	`pnpm lint` then `pnpm check:fix`
Tests	`pnpm test -- --filter=<file>`
Build	`pnpm build`

Debugging Steps

Check workflow logs in GitHub Actions UI
Reproduce failure locally with commands above
Fix the issue
Push fix to PR
Re-run failed jobs: gh run rerun <run-id>

npm Publish Rate Limiting

If npm publish fails: wait and retry. Check status at https://status.npmjs.org/

Secrets Management

Secret	Purpose	Where Set
`GITHUB_TOKEN`	Auto-provided	GitHub
`NPM_TOKEN`	npm publishing	Repository Settings > Secrets > Actions

Common Mistakes

Mistake	Fix
Missing `--frozen-lockfile`	Always use in CI installs
Using `@latest` action versions	Pin to specific versions (`@v4`)
No `concurrency` setting	Add to prevent duplicate runs
Forgetting to add changeset	Run `pnpm changeset` before PR

References

Skill Reference Files

Workflow Templates - Full YAML workflow definitions and reusable patterns
Troubleshooting Guide - Detailed debugging patterns

Project Resources

.github/workflows/ - Workflow files
.husky/ - Git hooks
.changeset/ - Changeset configuration

Related Skills

Creating releases: See creating-changesets for changeset creation
Local validation: See validating-pre-commit for reproducing CI checks locally

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: managing-github-cidescription: Configures GitHub Actions workflows and CI/CD pipelines. Use when creating workflow YAML, managing npm releases, troubleshooting CI failures, configuring Husky hooks, or setting up release automation. Do NOT use for local development commands or application code.---# GitHub CI Automation## OverviewGuide the configuration and management of GitHub Actions workflows, release automation, and CI/CD pipelines for the Saleor Configurator project.## When to Use- Creating or modifying GitHub Actions workflows- Setting up automated releases via Changesets- Troubleshooting CI failures- Configuring pre-commit/pre-push hooks (Husky)## Quick Reference| Workflow | Trigger | Purpose ||----------|---------|---------|| `test-on-pr.yml` | PR to main | Typecheck, lint, test, build || `release.yml` | Push to main | Changesets publish to npm || `changeset-bot.yml` | PR opened/synced | Comment on missing changesets |## Project CI Architecture```.github/├── workflows/│ ├── test-on-pr.yml # PR validation│ ├── release.yml # Automated releases│ └── changeset-bot.yml # Changeset automation.husky/├── pre-push # Schema docs generation.changeset/├── config.json # Changeset configuration└── *.md # Pending changesets```## Workflows### test-on-pr.ymlValidates PRs before merge. Runs: typecheck, lint, test, build. Uses pnpm 9 + Node 20.See [references/workflow-templates.md](references/workflow-templates.md) for full YAML.### Required Checks| Check | Command | Purpose ||-------|---------|---------|| Type check | `pnpm typecheck` | TypeScript validation || Lint | `pnpm lint` | Biome linting || Test | `pnpm test` | Vitest test suite || Build | `pnpm build` | Compilation check |### release.ymlAutomated npm releases via Changesets. Triggers on push to main with concurrency control.Uses `changesets/action@v1` with `pnpm publish:ci-prod`. Requires `GITHUB_TOKEN` and `NPM_TOKEN`.### Release Flow```1. Developer creates changeset -> pnpm changeset2. PR merged to main3. Changesets action runs: a. If changesets exist -> Creates "Version Packages" PR b. If version PR merged -> Publishes to npm```### changeset-bot.ymlComments on PRs about missing changesets. Uses `changesets/bot@v1`.## Pre-Push Hooks (Husky)Located in `.husky/pre-push`:- Runs `pnpm generate-schema-docs` before every push- Auto-commits schema documentation updates- Ensures docs stay in sync with schema changes## Changesets ConfigurationLocated in `.changeset/config.json`. Key settings: `access: "public"`, `baseBranch: "main"`.| Type | When to Use ||------|-------------|| `patch` | Bug fixes, documentation, refactoring || `minor` | New features, non-breaking enhancements || `major` | Breaking changes, API modifications |## GitHub CLIUse `gh` for workflow management: `gh run list`, `gh run view <id>`, `gh run watch <id>`, `gh run rerun <id>`, `gh pr checks <number>`.## Troubleshooting CI Failures### Reproduce Locally| Failure | Command ||---------|---------|| Type check | `pnpm typecheck` or `npx tsc --noEmit` || Lint | `pnpm lint` then `pnpm check:fix` || Tests | `pnpm test -- --filter=<file>` || Build | `pnpm build` |### Debugging Steps1. Check workflow logs in GitHub Actions UI2. Reproduce failure locally with commands above3. Fix the issue4. Push fix to PR5. Re-run failed jobs: `gh run rerun <run-id>`### npm Publish Rate LimitingIf npm publish fails: wait and retry. Check status at https://status.npmjs.org/## Secrets Management| Secret | Purpose | Where Set ||--------|---------|-----------|| `GITHUB_TOKEN` | Auto-provided | GitHub || `NPM_TOKEN` | npm publishing | Repository Settings > Secrets > Actions |## Common Mistakes| Mistake | Fix ||---------|-----|| Missing `--frozen-lockfile` | Always use in CI installs || Using `@latest` action versions | Pin to specific versions (`@v4`) || No `concurrency` setting | Add to prevent duplicate runs || Forgetting to add changeset | Run `pnpm changeset` before PR |## References### Skill Reference Files- **[Workflow Templates](references/workflow-templates.md)** - Full YAML workflow definitions and reusable patterns- **[Troubleshooting Guide](references/troubleshooting.md)** - Detailed debugging patterns### Project Resources- `.github/workflows/` - Workflow files- `.husky/` - Git hooks- `.changeset/` - Changeset configuration## Related Skills- **Creating releases**: See `creating-changesets` for changeset creation- **Local validation**: See `validating-pre-commit` for reproducing CI checks locally---> Converted and distributed by [TomeVault](https://tomevault.io/claim/saleor) — claim your Tome and manage your conversions.

Frequently asked questions