* docs: sync all tutorials with latest Claude Code official docs (April 2026) Update 44 documentation files to reflect the latest Claude Code features from code.claude.com. Key content changes include new slash commands (/ultraplan, /powerup, /sandbox), deprecated command removals (/pr-comments, /vim), corrected skill description budget (1%/8K), new hook events (PermissionDenied, InstructionsLoaded, ConfigChange), expanded Agent Teams section, new plugin components (LSP, bin/, settings.json), and new CLI flags (--bare, --tmux, --effort, --channels). Added "Last Updated: April 2026" metadata footer to all documentation files. * fix(docs): correct env var values and alphabetical ordering - CLAUDE_CODE_NEW_INIT=true → =1 in 02-memory and 09-advanced-features - CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=true → =1 in 09-advanced-features - Fix /powerup vs /plugin alphabetical order in slash commands table * fix(docs): correct env var values in locale files (vi, zh) Propagate CLAUDE_CODE_NEW_INIT=true → =1 and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=true → =1 corrections to Vietnamese and Chinese translations.
29 lines
1.0 KiB
Markdown
29 lines
1.0 KiB
Markdown
---
|
|
name: Setup CI/CD Pipeline
|
|
description: Implement pre-commit hooks and GitHub Actions for quality assurance
|
|
tags: ci-cd, devops, automation
|
|
---
|
|
|
|
# Setup CI/CD Pipeline
|
|
|
|
Implement comprehensive DevOps quality gates adapted to project type:
|
|
|
|
1. **Analyze project**: Detect language(s), framework, build system, and existing tooling
|
|
2. **Configure pre-commit hooks** with language-specific tools:
|
|
- Formatting: Prettier/Black/gofmt/rustfmt/etc.
|
|
- Linting: ESLint/Ruff/golangci-lint/Clippy/etc.
|
|
- Security: Bandit/gosec/cargo-audit/npm audit/etc.
|
|
- Type checking: TypeScript/mypy/flow (if applicable)
|
|
- Tests: Run relevant test suites
|
|
3. **Create GitHub Actions workflows** (.github/workflows/):
|
|
- Mirror pre-commit checks on push/PR
|
|
- Multi-version/platform matrix (if applicable)
|
|
- Build and test verification
|
|
- Deployment steps (if needed)
|
|
4. **Verify pipeline**: Test locally, create test PR, confirm all checks pass
|
|
|
|
Use free/open-source tools. Respect existing configs. Keep execution fast.
|
|
|
|
---
|
|
**Last Updated**: April 2026
|