
Workflow Setup
- 99 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
Bootstrap or extend GitHub Actions for test, lint, and deploy on Python, Rust, or TypeScript repos without hand-writing every workflow from scratch.
About
Workflow-setup is an agent skill that configures GitHub Actions CI/CD for solo and indie builders shipping Python, Rust, or TypeScript code. It walks a repeatable pipeline: read what already exists under .github/workflows, decide which test, lint, and deployment jobs are missing, materialize templates aligned to the detected stack, and validate the resulting YAML. The skill encodes opinionated best practices such as current action versions, Python matrix testing, and dependency caching so small teams get dependable automation without becoming GitHub Actions specialists. Use it when you spin up a new repository, inherit a project with no CI, or need to modernize brittle workflows before you rely on agents to merge and ship. It is procedural packaging for Claude Code, Cursor, and Codex—not a hosted runner or MCP server—so you still own secrets, branch protection, and deploy targets in GitHub.
- Four-step flow: audit existing workflows, gap missing jobs, render stack-specific templates, validate YAML
- Dedicated workflow sections for Python, Rust, and TypeScript with matrix testing and dependency caching guidance
- Targets **/.github/workflows/*.yml** globs and documents latest action versions and update practices
- Intermediate setup oriented to new repos, partial automation, and workflow refreshes
- Related-skills handoff for broader infra work in the same night-market bundle
Workflow Setup by the numbers
- 99 all-time installs (skills.sh)
- Ranked #550 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill workflow-setupAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 99 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Bootstrap or extend GitHub Actions for test, lint, and deploy on Python, Rust, or TypeScript repos without hand-writing every workflow from scratch.
Files
Table of Contents
- When To Use
- Standard Workflows
- Python Workflows
- Rust Workflows
- TypeScript Workflows
- Workflow
- 1. Check Existing Workflows
- 2. Identify Missing Workflows
- 3. Render Workflow Templates
- 4. Validate Workflows
- Workflow Best Practices
- Use Latest Action Versions
- Matrix Testing (Python)
- Caching Dependencies
- Updating Workflows
- Related Skills
Workflow Setup Skill
Set up GitHub Actions workflows for continuous integration and deployment.
When To Use
- Need CI/CD for a new project
- Adding missing workflows to existing project
- Updating workflow versions to latest
- Automating testing and quality checks
- Setting up deployment pipelines
When NOT To Use
- GitHub Actions workflows already configured and current
- Project uses different CI platform (GitLab CI, CircleCI, etc.)
- Not hosted on GitHub
- Use
/attune:upgrade-projectinstead for updating existing workflows
Standard Workflows
Python Workflows
1. test.yml - Run pytest on push/PR 2. lint.yml - Run ruff linting 3. typecheck.yml - Run mypy type checking 4. publish.yml - Publish to PyPI on release
Rust Workflows
1. ci.yml - Combined test/lint/check workflow 2. release.yml - Build and publish releases
TypeScript Workflows
1. test.yml - Run Jest tests 2. lint.yml - Run ESLint 3. build.yml - Build for production 4. deploy.yml - Deploy to hosting (Vercel, Netlify, etc.)
Workflow
1. Check Existing Workflows
ls -la .github/workflows/Verification: Run the command with --help flag to verify availability.
2. Identify Missing Workflows
from project_detector import ProjectDetector
detector = ProjectDetector(Path.cwd())
language = detector.detect_language()
required_workflows = {
"python": ["test.yml", "lint.yml", "typecheck.yml"],
"rust": ["ci.yml"],
"typescript": ["test.yml", "lint.yml", "build.yml"],
}
missing = detector.get_missing_configurations(language)Verification: Run pytest -v to verify tests pass.
3. Render Workflow Templates
workflows_dir = Path(".github/workflows")
workflows_dir.mkdir(parents=True, exist_ok=True)
for workflow in required_workflows[language]:
template = templates_dir / language / "workflows" / f"{workflow}.template"
output = workflows_dir / workflow
engine.render_file(template, output)
print(f"✓ Created: {output}")Verification: Run the command with --help flag to verify availability.
4. Validate Workflows
# Syntax check (requires act or gh CLI)
gh workflow list
# Or manually check YAML syntax
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/test.yml'))"Verification: Run pytest -v to verify tests pass.
Workflow Best Practices
Use Latest Action Versions
# Good - pinned to major version
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
# Avoid - unpinned or outdated
- uses: actions/checkout@v2
- uses: actions/setup-python@latestVerification: Run pytest -v to verify tests pass.
Matrix Testing (Python)
strategy:
matrix:
python-version: ["3.10", "3.11", "3.12"]
os: [ubuntu-latest, macos-latest, windows-latest]Verification: Run pytest -v to verify tests pass.
Caching Dependencies
- uses: actions/setup-python@v5
with:
python-version: '3.10'
cache: 'pip' # Cache pip dependenciesVerification: Run python --version to verify Python environment.
Shell Script Safety in Workflows
When writing inline shell scripts in workflows, ensure proper exit code handling:
# BAD - pipeline masks exit code
- run: |
make typecheck 2>&1 | grep -v "^make\["
echo "Typecheck passed" # Runs even if make failed!
# GOOD - use pipefail
- run: |
set -eo pipefail
make typecheck 2>&1 | grep -v "^make\["
# GOOD - capture exit code explicitly
- run: |
output=$(make typecheck 2>&1) || exit_code=$?
echo "$output" | grep -v "^make\[" || true
exit ${exit_code:-0}For complex wrapper scripts, run /pensive:shell-review before integrating.
Updating Workflows
To update workflows to latest versions:
/attune:upgrade-project --component workflowsVerification: Run the command with --help flag to verify availability.
Related Skills
Skill(attune:project-init)- Full project initializationSkill(sanctum:pr-prep)- PR preparation with CI checks
Exit Criteria
- [ ] All required workflow files for the detected language exist under
.github/workflows/
(Python: test.yml + lint.yml + typecheck.yml; Rust: ci.yml; TypeScript: test.yml + lint.yml + build.yml) and contain valid YAML syntax verified by python3 -c "import yaml; yaml.safe_load(open('...'))".
- [ ]
gh workflow listreturns each created workflow file as an entry, confirming GitHub
recognizes the workflow definitions.
- [ ] Any inline shell script in a workflow uses
set -eo pipefailor explicit exit-code
capture; pipeline-masked failures (cmd | grep) without pipefail are flagged as errors.
- [ ] If the project uses a CI platform other than GitHub Actions (GitLab CI, CircleCI), the
skill reports this incompatibility and stops rather than generating GitHub-specific files.
Related skills
FAQ
Is Workflow Setup safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.