|
|
|
|
|
|
by tinodb
257 days ago
|
|
|
We have a GH workflow that spins up Claude with a prompt like this and it works quite well: — You are going to create a summary of the important changes for a PR created by
dependabot: 1. Read the body of PR $ARGUMENTS with the `gh` cmdline tool.
2. Create a todo list for yourself for each package in PLAN.md.
3. For each todo, read the releases page(s) (add /releases to the github repo
url) to cover the update range.
4. Summarize breaking changes and CVE updates, see template at the end. Grouped
into Dev Dependencies and Production Dependencies.
5. For production dependencies, find code usages (with `rg`/`grep`) and
determine if breaking changes will affect us. Add a list of all found usages,
linking to the direct line on github (like
https://github.com/solarmonkey/app/blob/master/frontend/some...).
Finish each with a verdict: unsure/likely OK/*may break*/*SURELY
BREAKING*!
6. Fill the table up top with the verdicts
7. Write the filled out template to `deps_update_analysis.md`. Don't add a final
summary or conclusive thoughts. The template is all we need. [snip template to fill] |
|
|