dtctl-release
dtctl Release Process
This skill walks through shipping a new dtctl release end-to-end. The process has six phases: analyze, version, changelog, test, commit/tag/push, and GitHub release notes.
Prerequisites
- You must be on the
mainbranch with all feature branches merged - The working tree must be clean (
git statusshows no uncommitted changes) - If the user is on a feature branch, merge to main first (or ask them to)
Pre-flight check:
git branch --show-current # Must be "main"
git status # Must be clean
git pull origin main # Must be up to date with remote
If any check fails, stop and resolve before continuing.
More from dynatrace-oss/dtctl
dtctl
Investigate incidents, debug performance issues, analyze logs, and manage observability resources in Dynatrace using the dtctl CLI. Use this skill whenever the user asks about error rates, latency spikes, service health, crash-looping pods, web vitals, SLO status, open problems, root cause analysis, log patterns, trace analysis, or building dashboards — even if they don't mention Dynatrace by name. Also covers DQL queries, workflow management, notebook and dashboard creation, settings configuration, and any operations against a Dynatrace environment.
270pr-review
Perform a thorough quality review of a pull request or feature branch before merging. Use this skill whenever the user asks to review a PR, check if code is production-ready, assess quality, verify docs are updated, or asks "is this ready to merge?", "review this PR", "check quality", "is this production ready?", or similar. Also use when reviewing your own work before submitting.
69