Devops quality
Code quality standards, linting rules, and CI/CD principles.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill devops-qualityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 190 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it: 1 file
13.4 KB alongside SKILL.md
- skill-report.json13.4 KB