Install
$ agentstack add skill-pavel-molyanov-molyanov-ai-dev-deploy-pipeline ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Deploy Pipeline
Project Documentation Autosync
Project documentation source of truth is Claude-side: CLAUDE.md and .claude/**. Codex-side AGENTS.md and .codex/** are generated runtime files.
After changing any project-local .claude/** file, immediately run:
~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply
If sync reports a conflict, stop and report it. Include generated .codex/** changes in the same commit as the .claude/** source change.
Gathering Deployment Context
Read project-knowledge to understand the deployment target:
.claude/skills/project-knowledge/references/deployment.md.claude/skills/project-knowledge/references/architecture.md.claude/skills/project-knowledge/references/patterns.md
If deployment target is not documented, ask the user:
- Target platform (Vercel, Railway, Fly.io, AWS ECS, VPS, NPM, Chrome Web Store)
- Environment details (URLs, project/service IDs, server access)
- Required secrets and where to obtain them
After gathering answers, immediately update deployment.md before proceeding with setup.
CI/CD Convention
Create .github/workflows/ci.yml following this structure:
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
check-skip:
runs-on: ubuntu-latest
outputs:
should_skip: ${{ steps.check.outputs.should_skip }}
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 2
- id: check
run: |
FILES=$(git diff --name-only HEAD~1 HEAD 2>/dev/null || git diff --name-only HEAD)
if echo "$FILES" | grep -vqE '\.(md|txt)$|^\.claude/|^\.spec/|^docs/'; then
echo "should_skip=false" >> $GITHUB_OUTPUT
else
echo "should_skip=true" >> $GITHUB_OUTPUT
fi
test:
needs: check-skip
if: needs.check-skip.outputs.should_skip != 'true'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# setup, install, lint, type-check, test, build
deploy:
needs: test
if: github.ref == 'refs/heads/main' && github.event_name == 'push'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# platform-specific deploy action
Adapt: add language setup, install steps, platform-specific deploy action.
Platform Selection
| Platform | Choose when | |----------|------------| | Vercel | Next.js, React, static sites, serverless | | Railway | Full-stack apps needing managed DB | | Fly.io | Docker containers, global edge | | AWS ECS | Enterprise, full infrastructure control | | Custom VPS | Persistent sessions, multi-device | | NPM | Node.js packages or CLI tools | | Chrome Web Store | Browser extensions |
For VPS deployments: server-specific details (IPs, SSH keys, paths) go to deployment.md.
Secrets Convention
Document all required secrets in .claude/skills/project-knowledge/references/deployment.md. For each secret:
- Name (GitHub Actions key)
- Where to obtain value (dashboard URL or CLI command)
- Which workflow uses it
Guide user to add secrets in GitHub repository settings. Create .env.example with application-level variable names.
Documentation Updates
After configuring, update project-knowledge references. Append to existing content.
deployment.md: deploy target, pipeline overview, required secrets table, manual deploy command, rollback steps.
patterns.md (Git Workflow section): CI triggers, pipeline jobs, skip logic pattern, PR workflow.
Decision Framework
Add deploy job? YES if: deployment target defined, user requests it, stable main branch. NO if: early development, manual deploys preferred, manual review step needed (Chrome Web Store).
Use matrix strategy? YES if: NPM package, cross-platform library. NO if: single-environment app, internal tool.
Add staging? YES if: project uses main + dev branches (default workflow). NO if: Vercel preview deploys sufficient.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: pavel-molyanov
- Source: pavel-molyanov/molyanov-ai-dev
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.