deployment-devops-workflow
Skill10 starsChanged 4 months agoMITView on GitHub
CI/CD pipelines, deployment automation, and monitoring for design systems. Use this skill for GitHub Actions workflow setup, automated testing and building, deployment strategies, versioning and tagging, rollback procedures, performance monitoring, and team collaboration in deployment pipelines.
- Installs packages
- Sends data out
- Commits and pushes
In this repository14 other files it gives its agents.
- anti-ai-design-patternsSkill
- component-library-masterySkill
- css-styling-pixel-perfectSkill
- design-fundamentalsSkill
- design-systems-architectureSkill
- design-to-code-workflowSkill
- design-tokens-systemSkill
- figma-expert-workflowsSkill
- frontend-framework-guideSkill
- inclusive-design-patternsSkill
- qa-testing-visual-regressionSkill
- responsive-universal-designSkill
- web-accessibility-a11ySkill
- web-performance-optimizationSkill
The file
Files
Deployment & DevOps Workflow
Automated CI/CD pipelines for design system deployment and monitoring.
Reliable deployment means changes flow smoothly from development through testing to production, with rollback options if needed.
GitHub Actions Basics
Workflow Structure
# .github/workflows/deploy.yml
name: Deploy
on:
push:
branches: [main]
jobs:
build-test-deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci
- run: npm run lint
- run: npm test
- run: npm run build
- run: npm publishTrigger Conditions
on:
push:
branches: [main]
paths: ['src/**', 'package.json']
pull_request:
types: [opened, synchronize]
release:
types: [published]Build & Test Pipeline
Lint & Type Check
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci
- run: npm run lint # ESLint
- run: npm run type-check # TypeScriptUnit Tests
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci
- run: npm test -- --coverage
- uses: codecov/codecov-action@v3Visual Tests
jobs:
visual:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci
- run: npm run build-storybook
- uses: chromaui/action@v1
with:
projectToken: ${{ secrets.CHROMATIC_TOKEN }}Versioning & Release
Semantic Versioning
jobs:
version:
runs-on: ubuntu-latest
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci
- name: Bump version
run: |
npm version patch -m "Release v%s"
git push --follow-tagsAutomated Changelog
jobs:
changelog:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Generate changelog
run: npx changelog-cli generate
- name: Commit changelog
run: |
git add CHANGELOG.md
git commit -m "Update changelog"
git pushDeployment Strategies
Strategy 1: Automatic Publish on Main
name: Deploy
on:
push:
branches: [main]
jobs:
publish:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
registry-url: https://registry.npmjs.org
- run: npm ci && npm run build && npm publish
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}Strategy 2: Manual Release (Recommended for Breaking Changes)
name: Deploy
on:
release:
types: [published]
jobs:
publish:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: ${{ github.event.release.tag_name }}
- uses: actions/setup-node@v3
with:
registry-url: https://registry.npmjs.org
- run: npm ci && npm run build && npm publish
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}Strategy 3: Canary Deployment
jobs:
publish-canary:
runs-on: ubuntu-latest
if: github.ref != 'refs/heads/main'
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
registry-url: https://registry.npmjs.org
- run: |
npm ci && npm run build
npm publish --tag canary
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}Monitoring & Rollback
Health Checks
jobs:
smoke-test:
runs-on: ubuntu-latest
needs: publish
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: |
npm install @company/component-library@latest
npm test -- integration.test.tsRollback Procedure
# If critical issue detected
npm unpublish @company/component-library@1.2.0
# Or publish old version as latest
npm publish --tag latest
# Notify team
curl -X POST https://slack.com/api/chat.postMessage \
-H 'Content-Type: application/json' \
-d '{
"channel":"#devops",
"text":"ROLLBACK: Reverted to v1.1.0"
}'Complete Example Pipeline
name: Deploy Pipeline
on:
push:
branches: [main, develop]
pull_request:
release:
types: [published]
jobs:
# Stage 1: Lint & Test
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci && npm run lint && npm run type-check
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci && npm test -- --coverage
- uses: codecov/codecov-action@v3
visual:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci && npm run build-storybook
- uses: chromaui/action@v1
with:
projectToken: ${{ secrets.CHROMATIC_TOKEN }}
# Stage 2: Build
build:
needs: [lint, test, visual]
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci && npm run build
- uses: actions/upload-artifact@v3
with:
name: dist
path: dist
# Stage 3: Deploy (only on release or main push)
publish:
needs: build
runs-on: ubuntu-latest
if: github.event_name == 'release' || (github.event_name == 'push' && github.ref == 'refs/heads/main')
steps:
- uses: actions/checkout@v3
- uses: actions/download-artifact@v3
with:
name: dist
- uses: actions/setup-node@v3
with:
registry-url: https://registry.npmjs.org
- run: npm publish
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
# Stage 4: Notify
notify:
needs: publish
if: always()
runs-on: ubuntu-latest
steps:
- name: Slack Notification
run: |
curl -X POST ${{ secrets.SLACK_WEBHOOK }} \
-H 'Content-Type: application/json' \
-d '{"text":"Component library v${{ github.ref }} deployed"}'Test Cases: 6 Scenarios
Test 1: Automated Linting & Testing
Lint, type check, and unit tests run on PR Result: ✅ PASS
Test 2: Visual Regression in CI
Visual tests block merge if regression detected Result: ✅ PASS
Test 3: Automated Versioning
Bump version, tag, and push on main merge Result: ✅ PASS
Test 4: npm Publishing
Build and publish to npm automatically Result: ✅ PASS
Test 5: Canary Deployment
Pre-release canary version for testing Result: ✅ PASS
Test 6: Rollback Procedure
Unpublish or revert to previous version Result: ✅ PASS
Summary: 6/6 tests passing ✅
🎉 TIER 3 COMPLETE! 🎉
All 5 Workflow Integration Skills Done:
- Skill #10: design-to-code-workflow ✅
- Skill #11: component-library-mastery ✅
- Skill #12: design-tokens-system ✅
- Skill #13: qa-testing-visual-regression ✅
- Skill #14: deployment-devops-workflow ✅
Status: 14/14 skills complete! Master Skills Architecture FINISHED! 🚀
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

