devops-quality
Code quality standards, linting rules, and CI/CD principles.
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for maintaining high code quality and robust DevOps practices. It integrates strict linting rules, semantic versioning, and CI/CD principles to streamline the software development lifecycle, ensuring consistent code formatting, automated testing, and secure deployment workflows.
Use Cases
- Automating code quality checks using ESLint and TypeScript to maintain a clean and error-free codebase.
- Standardizing version control workflows through semantic commit messages and structured branching strategies.
- Implementing Continuous Integration (CI) pipelines with GitHub Actions to automate builds and unit/E2E testing on every pull request.
- Securing sensitive information by establishing best practices for local and production environment variable management.
| name | DevOps & Quality |
|---|---|
| description | Code quality standards, linting rules, and CI/CD principles. |
DevOps & Code Quality
Linting & Formatting
- Tool: ESLint (
npm run lint). - Config:
eslint.config.mjs/next.config.ts. - Rule: strict type checking is enabled in
tsconfig.json.
Version Control
- Branching: Feature branch workflow (main <- feature/xyz).
- Commit Messages: Semantic commits preferred (e.g.,
feat: add chatbot,fix: header overflow).
Continuous Integration (CI)
(Future Implementation)
- GitHub Actions: Recommended for running
npm run lintandnpm run buildon every PR. - Testing:
- Unit: Jest (for utility logic).
- E2E: Playwright (for auth flows).
Secrets Management
- Local:
.envfile (never committed). - Production: Vercel Environment Variables.