shalin-rahman/skills/devops-cicd
skills/devops-cicd/SKILL.md
# Skill: CI/CD & DevOps Best Practices (Staff Engineer) # Usage: Use when configuring pipelines, deployments, and operational infrastructure. ## 🚀 Continuous Integration (CI) - **Automated Testing**: Every push must trigger a comprehensive suite of Unit and Integration tests. The build must fail if tests fail. - **Static Analysis & Linting**: Enforce code style and quality gates automatically. The build must fail on critical code smells or security flaws. - **Fast Feedback**: The CI loop shoul
$ install --global
skillsauthnpx skillsauth add shalin-rahman/Synapticity skills/devops-cicdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 12:45 AM186.4s1 file scanned
SKILL.md
Skill: CI/CD & DevOps Best Practices (Staff Engineer)
Usage: Use when configuring pipelines, deployments, and operational infrastructure.
🚀 Continuous Integration (CI)
- Automated Testing: Every push must trigger a comprehensive suite of Unit and Integration tests. The build must fail if tests fail.
- Static Analysis & Linting: Enforce code style and quality gates automatically. The build must fail on critical code smells or security flaws.
- Fast Feedback: The CI loop should be as fast as possible to keep developers productive.
- Immutable Artifacts: Build once, deploy many. The exact same container/artifact tested in CI must be what runs in Production.
🚢 Continuous Deployment / Delivery (CD)
- Zero-Downtime Deployments: Use strategies like Blue/Green, Canary, or Rolling Updates.
- Infrastructure as Code (IaC): Provision and manage infrastructure using code (Terraform, CloudFormation, Bicep). Never configure environments manually via a UI console.
- Configuration Management: Externalize configurations. Applications should read configs from Environment Variables or secure stores (e.g., Azure Key Vault, AWS Secrets Manager), not hardcoded files.
🔭 Observability & Telemetry
- Structured Logging: Log in JSON format to allow easy searching and indexing in tools like ELK, Datadog, or Application Insights.
- Correlation IDs: Attach a unique request ID to every incoming request and pass it through all downstream services to trace the entire lifecycle of a transaction.
- Health Checks: Expose a
/healthor/readyendpoint so load balancers and orchestrators (like Kubernetes) know the application's state.
🔐 DevSecOps
- Shift Left Security: Integrate security scans (SAST, DAST, dependency checking) directly into the CI pipeline.
- Secret Hygiene: Never commit secrets to version control. Use secret management tools.
- Principle of Least Privilege: Grant applications and CI runners only the minimum permissions necessary to perform their tasks.
🚫 Anti-Patterns
- Manual deployments or "copying files to the server".
- Committing secrets or API keys to the repository.
- Treating Infrastructure as "pets" (hand-crafted, hard to replace) rather than "cattle" (easily replaceable, reproducible via code).
Related Skills
shalin-rahman/skills/zero-defect-engineering
tools
VerifiedTrustedCommunity
# Skill: Zero-Defect Software Engineering # Focus: Writing immortal, self-documenting, and resilient source code. ## Playbook Strategy: 1. **SOLID Foundations**: - **Single Responsibility**: Every class/function does ONE thing perfectly. - **Open/Closed**: Design for extension without modification. 2. **DRY (Don't Repeat Yourself)**: If logic appears twice, abstract it into a utility or base class. 3. **Defensive Programming**: - Validate every input. - Handle every exception specif
1SKILL.mdUpdated Apr 22, 2026
shalin-rahman/skills/typescript-clean
development
VerifiedTrustedCommunity
# Skill: TypeScript Clean Code (Staff Engineer) # Usage: Use for any TypeScript-based project to ensure enterprise-grade type safety and readability. ## Core Rules: - **Strict Typing:** Never use `any`. Use `unknown` with type guards if the type is truly uncertain. - **Interfaces vs Types:** Use `interface` for public APIs (extendability) and `type` for unions, intersections, and primitives. - **Functional Patterns:** Prioritize immutability. Use `readonly` for arrays and objects where possible
1SKILL.mdUpdated Apr 22, 2026
shalin-rahman/skills/testing-strategies
development
VerifiedTrustedCommunity
# Skill: Advanced Testing Strategies (TDD / BDD) # Usage: Use to enforce high code quality, prevent regressions, and ensure requirements are met implicitly. ## 🧪 The Testing Pyramid - **Unit Tests (70%)**: Fast, isolated tests for individual functions and classes. Mock all external dependencies. - **Integration Tests (20%)**: Test the interaction between several units or external systems (e.g., Database, APIs). - **End-to-End (E2E) Tests (10%)**: Slow, brittle tests that verify the system as a
1SKILL.mdUpdated Apr 22, 2026
shalin-rahman/skills/technical-writing-standards
development
VerifiedTrustedCommunity
# Skill: Technical Hand-off & Clarity # Focus: Professional documentation for human and machine consumption. ## Playbook Strategy: 1. **The "ReadMe First" Rule**: Use structured, hierarchical markdown. High-level summary first, deep-dive implementation second. 2. **Contextual Grounding**: Explain the "Why" and the "How" for every project. 3. **Semantic Clarity**: Use industry-standard terminology. Avoid jargon where simple language suffices. 4. **Machine-Readable Annotations**: Include clear co
1SKILL.mdUpdated Apr 22, 2026