Menü
Does research on competitor's changelogs.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | summarize_changelog |
| description | Does research on competitor's changelogs. |
Use your web search tool to create a summary of recent changelogs entries from competitors over the last 2 weeks. If there are any important themes in common, point them out.
Specifically, check these links for each competitor:
https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md https://cursor.com/changelog https://docs.factory.ai/changelog/cli-updates https://ampcode.com/chronicle https://github.com/sst/opencode/releases https://developers.openai.com/codex/changelog/ https://www.conductor.build/blog https://github.blog/changelog/?label=copilot&opened-months=2
YOU MUST INCLUDE YOUR PRODUCT'S CHANGELOG IN YOUR ANALYSIS
Review your product's changelog at YOUR_PRODUCT_CHANGELOG_URL and compare your recent changes in the same time periods to competitors. Keep in mind, you don't know what was shipped previously, so in your comparison, think about the things each of the teams have shipped in that period. USE THIS CHANGELOG AS THE SOURCE OF TRUTH FOR YOUR PRODUCT'S CHANGELOG, don't rely on other web searches.
Setup required: Replace
YOUR_PRODUCT_CHANGELOG_URLwith your product's public changelog URL. If the page is behind a CDN cache, usecurlwith cache-busting headers to fetch fresh content:curl -sL -H "Cache-Control: no-cache" -H "Pragma: no-cache" "YOUR_PRODUCT_CHANGELOG_URL?_=$(date +%s)"
Finally, deduplicate information. Search for previous summaries you did in the folder reports/competitor_changelog_reports/, and don't repeat changelog entries that have been covered previously. However, you can reference these reports to influence your summary and analysis.
In your summary, note the dates each feature was shipped. (e.g. is it a monthly or weekly release)
The summary should follow this format:
---BEGIN FORMAT---
Competitive Changelog Analysis - Last 2 Weeks (Date range) TL;DR: [Summary of changes]
[Competitor] (version number) -[Date][Feature description] -[Date][Feature description] -[Date][Feature description]
COMMON THEMES [common themes]
[YOUR PRODUCT] Comparison Shipped: Competitors: Opportunity:
RISKS
---END FORMAT---
And here is an example post (note: competitor entries are real; replace the [YOUR PRODUCT] section with your own changelog data):
---BEGIN EXAMPLE---
Competitive Changelog Analysis - Last 2 Weeks (Jan 13-27, 2026) TL;DR: Major industry push toward agent skills/customization, multi-agent collaboration, and image generation. Enterprise features expanding across all tools.
CURSOR (v2.3-2.4)
CLAUDE CODE (v2.1.x)
FACTORY (v0.42-0.52)
AMP
OPENCODE (v1.1.32-34)
CODEX (v0.90-0.92)
CONDUCTOR (v0.28-0.29)
COMMON THEMES
[YOUR PRODUCT] COMPARISON (Jan 7-21) Shipped: [list features your product shipped in this period] Competitors ahead on: [areas where competitors have shipped ahead of you] Opportunity: [gaps you could close or areas to differentiate]
RISKS
---END EXAMPLE---
Make sure to return your entire summary in the proper format to the requester, don't truncate it.
When you are finished, create a PR with the new report in the folder reports/competitor_changelog_reports/
analyzes customer feedback across Email, GitHub, NPS, and churn cancellations.
Analyzes git history from a repository to summarize recent development activity, features in progress, and engineering priorities. Use when asked about what the team is working on, recent code changes, development velocity, or to prepare for planning/roadmap discussions.
Projects a customer's cost from prior usage data across seat-based, usage-based, and hybrid SaaS pricing models. Use when asked to "project cost", "estimate BYO cost", "estimate spend", "how much will this cost", "size a deal", or to build an enterprise-style usage/cost projection.
Does research on competitive features and creates a report.
Reads the most recent weekly product briefing, identifies P0 issues, researches them in the codebase, and spawns cloud coding agents to fix each one. Use when asked to "fix P0s", "address critical issues", or "work on top priorities from the briefing."
Posts messages to Slack via webhook.