@ngxtm/devkit 3.6.1 → 3.8.0

package/merged-commands/cost-optimization.md

@@ -0,0 +1,286 @@
+---
+name: cost-optimization
+description: Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
+---
+
+# Cloud Cost Optimization
+
+Strategies and patterns for optimizing cloud costs across AWS, Azure, and GCP.
+
+## Do not use this skill when
+
+- The task is unrelated to cloud cost optimization
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Purpose
+
+Implement systematic cost optimization strategies to reduce cloud spending while maintaining performance and reliability.
+
+## Use this skill when
+
+- Reduce cloud spending
+- Right-size resources
+- Implement cost governance
+- Optimize multi-cloud costs
+- Meet budget constraints
+
+## Cost Optimization Framework
+
+### 1. Visibility
+- Implement cost allocation tags
+- Use cloud cost management tools
+- Set up budget alerts
+- Create cost dashboards
+
+### 2. Right-Sizing
+- Analyze resource utilization
+- Downsize over-provisioned resources
+- Use auto-scaling
+- Remove idle resources
+
+### 3. Pricing Models
+- Use reserved capacity
+- Leverage spot/preemptible instances
+- Implement savings plans
+- Use committed use discounts
+
+### 4. Architecture Optimization
+- Use managed services
+- Implement caching
+- Optimize data transfer
+- Use lifecycle policies
+
+## AWS Cost Optimization
+
+### Reserved Instances
+```
+Savings: 30-72% vs On-Demand
+Term: 1 or 3 years
+Payment: All/Partial/No upfront
+Flexibility: Standard or Convertible
+```
+
+### Savings Plans
+```
+Compute Savings Plans: 66% savings
+EC2 Instance Savings Plans: 72% savings
+Applies to: EC2, Fargate, Lambda
+Flexible across: Instance families, regions, OS
+```
+
+### Spot Instances
+```
+Savings: Up to 90% vs On-Demand
+Best for: Batch jobs, CI/CD, stateless workloads
+Risk: 2-minute interruption notice
+Strategy: Mix with On-Demand for resilience
+```
+
+### S3 Cost Optimization
+```hcl
+resource "aws_s3_bucket_lifecycle_configuration" "example" {
+  bucket = aws_s3_bucket.example.id
+
+  rule {
+    id     = "transition-to-ia"
+    status = "Enabled"
+
+    transition {
+      days          = 30
+      storage_class = "STANDARD_IA"
+    }
+
+    transition {
+      days          = 90
+      storage_class = "GLACIER"
+    }
+
+    expiration {
+      days = 365
+    }
+  }
+}
+```
+
+## Azure Cost Optimization
+
+### Reserved VM Instances
+- 1 or 3 year terms
+- Up to 72% savings
+- Flexible sizing
+- Exchangeable
+
+### Azure Hybrid Benefit
+- Use existing Windows Server licenses
+- Up to 80% savings with RI
+- Available for Windows and SQL Server
+
+### Azure Advisor Recommendations
+- Right-size VMs
+- Delete unused resources
+- Use reserved capacity
+- Optimize storage
+
+## GCP Cost Optimization
+
+### Committed Use Discounts
+- 1 or 3 year commitment
+- Up to 57% savings
+- Applies to vCPUs and memory
+- Resource-based or spend-based
+
+### Sustained Use Discounts
+- Automatic discounts
+- Up to 30% for running instances
+- No commitment required
+- Applies to Compute Engine, GKE
+
+### Preemptible VMs
+- Up to 80% savings
+- 24-hour maximum runtime
+- Best for batch workloads
+
+## Tagging Strategy
+
+### AWS Tagging
+```hcl
+locals {
+  common_tags = {
+    Environment = "production"
+    Project     = "my-project"
+    CostCenter  = "engineering"
+    Owner       = "team@example.com"
+    ManagedBy   = "terraform"
+  }
+}
+
+resource "aws_instance" "example" {
+  ami           = "ami-12345678"
+  instance_type = "t3.medium"
+
+  tags = merge(
+    local.common_tags,
+    {
+      Name = "web-server"
+    }
+  )
+}
+```
+
+**Reference:** See `references/tagging-standards.md`
+
+## Cost Monitoring
+
+### Budget Alerts
+```hcl
+# AWS Budget
+resource "aws_budgets_budget" "monthly" {
+  name              = "monthly-budget"
+  budget_type       = "COST"
+  limit_amount      = "1000"
+  limit_unit        = "USD"
+  time_period_start = "2024-01-01_00:00"
+  time_unit         = "MONTHLY"
+
+  notification {
+    comparison_operator        = "GREATER_THAN"
+    threshold                  = 80
+    threshold_type            = "PERCENTAGE"
+    notification_type         = "ACTUAL"
+    subscriber_email_addresses = ["team@example.com"]
+  }
+}
+```
+
+### Cost Anomaly Detection
+- AWS Cost Anomaly Detection
+- Azure Cost Management alerts
+- GCP Budget alerts
+
+## Architecture Patterns
+
+### Pattern 1: Serverless First
+- Use Lambda/Functions for event-driven
+- Pay only for execution time
+- Auto-scaling included
+- No idle costs
+
+### Pattern 2: Right-Sized Databases
+```
+Development: t3.small RDS
+Staging: t3.large RDS
+Production: r6g.2xlarge RDS with read replicas
+```
+
+### Pattern 3: Multi-Tier Storage
+```
+Hot data: S3 Standard
+Warm data: S3 Standard-IA (30 days)
+Cold data: S3 Glacier (90 days)
+Archive: S3 Deep Archive (365 days)
+```
+
+### Pattern 4: Auto-Scaling
+```hcl
+resource "aws_autoscaling_policy" "scale_up" {
+  name                   = "scale-up"
+  scaling_adjustment     = 2
+  adjustment_type        = "ChangeInCapacity"
+  cooldown              = 300
+  autoscaling_group_name = aws_autoscaling_group.main.name
+}
+
+resource "aws_cloudwatch_metric_alarm" "cpu_high" {
+  alarm_name          = "cpu-high"
+  comparison_operator = "GreaterThanThreshold"
+  evaluation_periods  = "2"
+  metric_name         = "CPUUtilization"
+  namespace           = "AWS/EC2"
+  period              = "60"
+  statistic           = "Average"
+  threshold           = "80"
+  alarm_actions       = [aws_autoscaling_policy.scale_up.arn]
+}
+```
+
+## Cost Optimization Checklist
+
+- [ ] Implement cost allocation tags
+- [ ] Delete unused resources (EBS, EIPs, snapshots)
+- [ ] Right-size instances based on utilization
+- [ ] Use reserved capacity for steady workloads
+- [ ] Implement auto-scaling
+- [ ] Optimize storage classes
+- [ ] Use lifecycle policies
+- [ ] Enable cost anomaly detection
+- [ ] Set budget alerts
+- [ ] Review costs weekly
+- [ ] Use spot/preemptible instances
+- [ ] Optimize data transfer costs
+- [ ] Implement caching layers
+- [ ] Use managed services
+- [ ] Monitor and optimize continuously
+
+## Tools
+
+- **AWS:** Cost Explorer, Cost Anomaly Detection, Compute Optimizer
+- **Azure:** Cost Management, Advisor
+- **GCP:** Cost Management, Recommender
+- **Multi-cloud:** CloudHealth, Cloudability, Kubecost
+
+## Reference Files
+
+- `references/tagging-standards.md` - Tagging conventions
+- `assets/cost-analysis-template.xlsx` - Cost analysis spreadsheet
+
+## Related Skills
+
+- `terraform-module-library` - For resource provisioning
+- `multi-cloud-architecture` - For cloud selection

package/merged-commands/cpp-pro.md

@@ -0,0 +1,59 @@
+---
+name: cpp-pro
+description: Write idiomatic C++ code with modern features, RAII, smart
+  pointers, and STL algorithms. Handles templates, move semantics, and
+  performance optimization. Use PROACTIVELY for C++ refactoring, memory safety,
+  or complex C++ patterns.
+metadata:
+  model: opus
+---
+
+## Use this skill when
+
+- Working on cpp pro tasks or workflows
+- Needing guidance, best practices, or checklists for cpp pro
+
+## Do not use this skill when
+
+- The task is unrelated to cpp pro
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are a C++ programming expert specializing in modern C++ and high-performance software.
+
+## Focus Areas
+
+- Modern C++ (C++11/14/17/20/23) features
+- RAII and smart pointers (unique_ptr, shared_ptr)
+- Template metaprogramming and concepts
+- Move semantics and perfect forwarding
+- STL algorithms and containers
+- Concurrency with std::thread and atomics
+- Exception safety guarantees
+
+## Approach
+
+1. Prefer stack allocation and RAII over manual memory management
+2. Use smart pointers when heap allocation is necessary
+3. Follow the Rule of Zero/Three/Five
+4. Use const correctness and constexpr where applicable
+5. Leverage STL algorithms over raw loops
+6. Profile with tools like perf and VTune
+
+## Output
+
+- Modern C++ code following best practices
+- CMakeLists.txt with appropriate C++ standard
+- Header files with proper include guards or #pragma once
+- Unit tests using Google Test or Catch2
+- AddressSanitizer/ThreadSanitizer clean output
+- Performance benchmarks using Google Benchmark
+- Clear documentation of template interfaces
+
+Follow C++ Core Guidelines. Prefer compile-time errors over runtime errors.

package/merged-commands/cqrs-implementation.md

@@ -0,0 +1,35 @@
+---
+name: cqrs-implementation
+description: Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
+---
+
+# CQRS Implementation
+
+Comprehensive guide to implementing CQRS (Command Query Responsibility Segregation) patterns.
+
+## Use this skill when
+
+- Separating read and write concerns
+- Scaling reads independently from writes
+- Building event-sourced systems
+- Optimizing complex query scenarios
+- Different read/write data models are needed
+- High-performance reporting is required
+
+## Do not use this skill when
+
+- The domain is simple and CRUD is sufficient
+- You cannot operate separate read/write models
+- Strong immediate consistency is required everywhere
+
+## Instructions
+
+- Identify read/write workloads and consistency needs.
+- Define command and query models with clear boundaries.
+- Implement read model projections and synchronization.
+- Validate performance, recovery, and failure modes.
+- If detailed patterns are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed CQRS patterns and templates.

package/merged-commands/create-pr.md

@@ -0,0 +1,192 @@
+---
+name: create-pr
+description: "Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines."
+source: "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/create-pr"
+risk: safe
+---
+
+# Create Pull Request
+
+Create pull requests following Sentry's engineering practices.
+
+## When to Use This Skill
+
+Use this skill when:
+- Opening pull requests
+- Writing PR descriptions
+- Preparing changes for review
+- Following Sentry's code review guidelines
+- Creating PRs that follow best practices
+
+**Requires**: GitHub CLI (`gh`) authenticated and available.
+
+## Prerequisites
+
+Before creating a PR, ensure all changes are committed. If there are uncommitted changes, run the `sentry-skills:commit` skill first to commit them properly.
+
+```bash
+# Check for uncommitted changes
+git status --porcelain
+```
+
+If the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the `sentry-skills:commit` skill before proceeding.
+
+## Process
+
+### Step 1: Verify Branch State
+
+```bash
+# Detect the default branch
+BASE=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
+
+# Check current branch and status
+git status
+git log $BASE..HEAD --oneline
+```
+
+Ensure:
+- All changes are committed
+- Branch is up to date with remote
+- Changes are rebased on the base branch if needed
+
+### Step 2: Analyze Changes
+
+Review what will be included in the PR:
+
+```bash
+# See all commits that will be in the PR
+git log $BASE..HEAD
+
+# See the full diff
+git diff $BASE...HEAD
+```
+
+Understand the scope and purpose of all changes before writing the description.
+
+### Step 3: Write the PR Description
+
+Use this structure for PR descriptions (ignoring any repository PR templates):
+
+```markdown
+<brief description of what the PR does>
+
+<why these changes are being made - the motivation>
+
+<alternative approaches considered, if any>
+
+<any additional context reviewers need>
+```
+
+**Do NOT include:**
+- "Test plan" sections
+- Checkbox lists of testing steps
+- Redundant summaries of the diff
+
+**Do include:**
+- Clear explanation of what and why
+- Links to relevant issues or tickets
+- Context that isn't obvious from the code
+- Notes on specific areas that need careful review
+
+### Step 4: Create the PR
+
+```bash
+gh pr create --draft --title "<type>(<scope>): <description>" --body "$(cat <<'EOF'
+<description body here>
+EOF
+)"
+```
+
+**Title format** follows commit conventions:
+- `feat(scope): Add new feature`
+- `fix(scope): Fix the bug`
+- `ref: Refactor something`
+
+## PR Description Examples
+
+### Feature PR
+
+```markdown
+Add Slack thread replies for alert notifications
+
+When an alert is updated or resolved, we now post a reply to the original
+Slack thread instead of creating a new message. This keeps related
+notifications grouped and reduces channel noise.
+
+Previously considered posting edits to the original message, but threading
+better preserves the timeline of events and works when the original message
+is older than Slack's edit window.
+
+Refs SENTRY-1234
+```
+
+### Bug Fix PR
+
+```markdown
+Handle null response in user API endpoint
+
+The user endpoint could return null for soft-deleted accounts, causing
+dashboard crashes when accessing user properties. This adds a null check
+and returns a proper 404 response.
+
+Found while investigating SENTRY-5678.
+
+Fixes SENTRY-5678
+```
+
+### Refactor PR
+
+```markdown
+Extract validation logic to shared module
+
+Moves duplicate validation code from the alerts, issues, and projects
+endpoints into a shared validator class. No behavior change.
+
+This prepares for adding new validation rules in SENTRY-9999 without
+duplicating logic across endpoints.
+```
+
+## Issue References
+
+Reference issues in the PR body:
+
+| Syntax | Effect |
+|--------|--------|
+| `Fixes #1234` | Closes GitHub issue on merge |
+| `Fixes SENTRY-1234` | Closes Sentry issue |
+| `Refs GH-1234` | Links without closing |
+| `Refs LINEAR-ABC-123` | Links Linear issue |
+
+## Guidelines
+
+- **One PR per feature/fix** - Don't bundle unrelated changes
+- **Keep PRs reviewable** - Smaller PRs get faster, better reviews
+- **Explain the why** - Code shows what; description explains why
+- **Mark WIP early** - Use draft PRs for early feedback
+
+## Editing Existing PRs
+
+If you need to update a PR after creation, use `gh api` instead of `gh pr edit`:
+
+```bash
+# Update PR description
+gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER -f body="$(cat <<'EOF'
+Updated description here
+EOF
+)"
+
+# Update PR title
+gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER -f title='new: Title here'
+
+# Update both
+gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER \
+  -f title='new: Title' \
+  -f body='New description'
+```
+
+Note: `gh pr edit` is currently broken due to GitHub's Projects (classic) deprecation.
+
+## References
+
+- [Sentry Code Review Guidelines](https://develop.sentry.dev/engineering-practices/code-review/)
+- [Sentry Commit Messages](https://develop.sentry.dev/engineering-practices/commit-messages/)