feature: change the pr-summarizer to sonnet, change-log to opus

Author: cdxker

.claude/agents/pr-summarizer.md

@@ -1,7 +1,7 @@
 ---
 name: pr-summarizer
 description: Use this agent when you need to analyze a GitHub pull request and create a concise summary of its description, body, and comments. This agent should be invoked with a repository name and PR number to generate a summary file in the summaries/ directory. Examples:\n\n<example>\nContext: User wants to summarize a pull request for documentation purposes.\nuser: "Summarize PR #142 from the facebook/react repository"\nassistant: "I'll use the pr-summarizer agent to analyze and summarize that pull request."\n<commentary>\nThe user is asking for a PR summary, so I should use the Task tool to launch the pr-summarizer agent with the repository and PR number.\n</commentary>\n</example>\n\n<example>\nContext: User needs to quickly understand what a PR is about without reading through all comments.\nuser: "Can you create a summary of pull request 89 in the vercel/next.js repo?"\nassistant: "Let me use the pr-summarizer agent to generate a concise summary of that PR."\n<commentary>\nThis is a clear request for PR summarization, so the pr-summarizer agent should be invoked via the Task tool.\n</commentary>\n</example>
-model: haiku
+model: sonnet
 color: yellow
 ---
 

.claude/commands/update-change-log.md

@@ -1,17 +1,19 @@
 ---
 allowed-tools: Bash(gh pr list *)
 description: Generate a new change log for a date time
+agent: opus
 argument-hint: [...repo]
 ---
 
 1. Update the changelog in @changelog.mdx for any updates that happened within the next date range.
 2. Tell me what date range of repositories you want to look at.
-3. Look at the repositories in #ARGUMENTS.
-4. We do not use releases. Only look at closed Pull Requests within the next daterange.
-5. For each pull request, invoke @agents-pr-summarizer in parallel to generate a summary of the pull request.
-6. Read each file from this in @summaries and generate a synopsis for each PR.
-7. Tell me a summary of what was changed
-8. Update @channgelog.mdx with the summary from all previous pull requests
+3. Keep the date range consistent with the previous changelog update. Only make one change log update.
+4. Look at the repositories in #ARGUMENTS.
+5. We do not use releases. Only look at closed Pull Requests within the next daterange.
+6. For each pull request, invoke @agents-pr-summarizer in parallel to generate a summary of the pull request.
+7. Read each file from this in @summaries and generate a synopsis for each PR.
+8. Tell me a summary of what was changed
+9. Update @channgelog.mdx with the summary from all previous pull requests
 
 This summary should be a high level overview.
 - Bug fixes should be highlighted.