Menu
Use renovate-dryrun to test Renovate configuration locally. Use this skill when debugging or validating renovate.json5 changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | debug-renovate |
| description | Use renovate-dryrun to test Renovate configuration locally. Use this skill when debugging or validating renovate.json5 changes. |
Test Renovate configuration changes locally with the renovate-dryrun command. This wrapper script runs Renovate in dry-run mode against the current repository and displays a formatted summary of proposed updates.
# Basic usage
renovate-dryrun --token $GH_TOKEN > .z/renovate-dryrun.log
# Test specific branch (defaults to current branch)
renovate-dryrun --token $GH_TOKEN --branch feature/update-deps > .z/renovate-dryrun.log
# Debug mode with raw Renovate output
renovate-dryrun --token $GH_TOKEN --raw > .z/renovate-debug.log
The output displays proposed updates in this format:
[renovate/aws-5.x] chore(deps): update terraform aws to v5.68.0 (automerge: true)
depName: aws
version: 5.49.0 -> 5.68.0
datasource: terraform-provider
packageFile: terraform/tfaction/main.tf
renovate.json5 configuration file in the current directory. To validate:
# Validate renovate.json5 in current directory
npx --package renovate -c 'renovate-config-validator renovate.json5'
.z/ since the command takes time and produces extensive output:--token $GH_TOKEN. Use the $GH_TOKEN environment variable, not $GITHUB_TOKEN.Writes, edits, and creates dbt models following best practices. Use when user needs to create new dbt SQL models, update existing models, or convert raw SQL to dbt format. Handles staging, intermediate, and mart models with proper config blocks, CTEs, and documentation.
Apply Domain-Driven Design, Clean Architecture, CQRS, and command/query patterns to code reviews and feature design. Use when analyzing or designing code in Application, Service, Infrastructure, DataAccess, Validation, Domain, or Functions projects, or when addressing architectural concerns, layering, mapping, entities, value objects, repositories, or validators in the Rome Repair Order Service.
Analyzes and refactors code using Domain-Driven Design principles. Use when refactoring domain models, identifying DDD anti-patterns, improving domain clarity, or applying tactical/strategic DDD patterns.
Guide for DDD strategic design - analyzing domains through structured questioning, conducting stakeholder interviews (PM/domain experts/users), and producing Bounded Context analysis, Context Maps, and Ubiquitous Language. Use when user needs help understanding domain boundaries, planning domain interviews, or structuring DDD strategic artifacts.
Win competitive rounds: run a clean process, deliver value previews before asking, coordinate partners, and manage timelines. Use when you're trying to close a 'must win' deal against other funds.
End-to-end associate workflow with time-boxed gates: thesis -> sourcing -> meetings -> diligence -> memo, ending with either IC-ready memo or explicit kill decision. Use when you need to run the full pipeline for a sector or a specific deal.