chore(skills): add create-release skill#1909
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1909 +/- ##
==========================================
+ Coverage 71.62% 71.77% +0.14%
==========================================
Files 432 434 +2
Lines 69183 69962 +779
==========================================
+ Hits 49554 50212 +658
- Misses 19629 19750 +121
🚀 New features to boost your workflow:
|
🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: f58efb0 | Docs | Datadog PR Page | Give us feedback! |
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
Aaalibaba42
left a comment
There was a problem hiding this comment.
I'm generally uncomfortable with letting AI use git. Why can't this be a script instead of a skill ? Is there some non-deterministic / hard to anticipate aspects ? This looks pretty straight forward
|
It can be a script, I think the skill helps with discoverability since you don't have to know it exist for claude to use it. I can make it a script and have a skill to make the script discoverable. |
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
@Aaalibaba42's suggestions are good. LGTM after you apply them. I think you also have to assign the script a codeowner and add license headers.
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Add a claude skill to create a new release
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.