SuperPlane Changelog

Use this skill when the user wants a changelog of what was merged to main over a given time range (e.g. "since Monday", "last 5 days", "since last Friday"). Produce a single markdown file in tmp/ with a consistent structure and tone.

1. Determine time range

• User may say: "since Monday", "last 5 days", "since last Friday", "Feb 3 to now", "since v0.6.0", or a specific date.
• Compute: Start and end of the window. Use date and time (not just date) when the start is a version tag so that same-day commits before the tag are excluded.
  • Date-only ranges (e.g. "since Monday", "Feb 3 to now"): Start = date at midnight, end = today. For "last 5 days" use Monday to Friday; for "since last Friday" use that Friday through today.
  • Version-tag ranges (e.g. "since v0.6.0"): Start = exact commit timestamp of the tag (e.g. git log -1 --format="%cI" v0.6.0 for ISO 8601). End = now or a chosen end date. This ensures commits that landed the same calendar day but before the tag are not included.
• Git: Use git log --since="<start>" --format="%h %ad %s" main where <start> is:
  • For date-only: YYYY-MM-DD (e.g. 2026-02-03). Use --date=short in the format.
  • For version-tag: the tag's commit timestamp in ISO 8601 (e.g. 2026-02-01T15:30:00+00:00). Use --date=iso if you need to compare times. Only include in the changelog items whose commit/merge date is strictly after the start when using a tag.

2. Classify what landed