devops-quality
Apply DevOps code quality standards
This skill helps teams establish consistent code quality standards. It provides guidance on linting rules, version control workflows, and CI/CD practices to improve code reliability and maintainability.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「devops-quality」。 How do I set up GitHub Actions for CI?
預期結果:
- Create .github/workflows/ci.yml configuration file
- Trigger workflow on push to main and pull requests
- Run npm install, npm run lint, and npm run build steps
- Use matrix strategy for testing across Node versions
- Store test results and build artifacts for debugging
正在使用「devops-quality」。 What are semantic commits?
預期結果:
- Format: type(scope): description
- Types: feat for new features, fix for bug fixes
- Other types: docs, style, refactor, test, chore
- Example: feat(auth): add user login validation
正在使用「devops-quality」。 How do I avoid committing secrets?
預期結果:
- Add .env files to .gitignore immediately
- Never commit API keys, tokens, or passwords
- Use environment variables in production (Vercel, etc.)
- Use git hooks to scan for secrets before commit
安全審計
安全This is a pure documentation skill containing only markdown guidance on DevOps best practices. All 28 static findings are FALSE POSITIVES triggered by documentation references that the pattern matcher misclassified. The skill contains no executable code, scripts, network calls, or file system access beyond reading its own file. The skill-report.json explicitly lists zero risk factors and the audit confirms it is safe to publish.
風險因素
🌐 網路存取 (1)
📁 檔案系統存取 (1)
品質評分
你能建構什麼
Establish code standards
Set up consistent linting rules and code quality checks across your development team.
Design CI/CD pipelines
Plan GitHub Actions workflows that run lint and build checks on every pull request.
Learn best practices
Understand proper version control workflow and commit message conventions.
試試這些提示
How do I configure ESLint with strict type checking for my TypeScript project?
What is the semantic commit message format? Give me examples for features, fixes, and documentation changes.
How do I set up GitHub Actions to run npm run lint and npm run build on every pull request?
What are the best practices for managing secrets locally and in production environments? How do I avoid committing secrets?
最佳實務
- Run linting before every commit to catch issues early in development
- Use semantic commit messages for clear changelog generation and team coordination
- Never commit .env files or secrets to version control systems
避免
- Skipping lint checks to save time during development phases
- Committing sensitive data like API keys or passwords to the repository
- Merging code without running build and test steps in CI pipeline