name	changelog
description	Generate a weekly changelog entry and prepend it to documentation/changelog.md
argument-hint	<YYYY-MM-DD Monday date, e.g. 2025-03-03>
allowed-tools	["AskUserQuestion","Bash(gh issue view)","Bash(gh pr list)","Bash(gh pr view)","Bash(git )","Edit","Glob","Grep","Read","Skill(demo-video-watcher)"]

Generate a changelog entry for a specific week and prepend it to documentation/changelog.md.

Input

$ARGUMENTS should be a Monday date in YYYY-MM-DD format (e.g. 2025-03-03). If empty, default to the most recent past Monday.

Steps

Parse the date: Determine the Monday date from $ARGUMENTS or calculate the previous Monday.
Confirm with user: Show the target week (Monday to Sunday) and ask the user to confirm before proceeding.

Get commits: Run git log for commits between that Monday 12:00 UTC and the following Monday 12:00 UTC:

git log --oneline --format="%H %s" --after="<monday>T12:00:00Z" --before="<next-monday>T12:00:00Z" origin/main

Filter commits: Keep only commits with feat: or fix: prefixes. Discard chore: and everything else.
Match commits to PRs: For each commit, extract the PR number from (#N) in the commit message. If not found, run gh pr list --search "<sha>" --state merged --json number,title to find the PR.
Read PRs and linked issues: For each PR:
- Run gh pr view <N> --comments to read the PR body and comments
- Extract Refs #N references to find linked issues
- Run gh issue view <N> --comments to read linked issues and their comments
Watch demo videos: If any issue or PR comments contain video attachments, invoke the /demo-video-watcher skill on them to understand what the feature does.
Generate the entry: Create a markdown entry in this format:

## Week of <DD Mon YYYY>

### Features
- **Short title** -- User-facing description.

### Fixes
- **Short title** -- User-facing description.

---

Guidelines for writing entries:

Write from a user's perspective — what changed for them, not implementation details
Keep descriptions to one sentence
NEVER link to GitHub issues or PRs — the changelog is user-facing documentation, not a developer log
Omit the ### Features or ### Fixes section if there are none that week
Sort entries alphabetically by title within each section
If a commit included an update to /documentation, link to the updated documentation page.

Insert the entry: Use the Edit tool to insert the generated entry immediately after the  line in documentation/changelog.md.
Show the result: Display the generated entry to the user for review. Do not commit — let the user decide.

Más de este repositorio

mismo repositorio

demo-video-watcher

teamniteo/claude

Watch demo videos linked in GitHub issue/PR comments. Downloads the video, transcribes audio with whisper and extracts frames. Use when encountering a video URL in a teamniteo or mayetrx repository.

2026-07-141

re-main

teamniteo/claude

Re(base) main — rebase the current branch on the repo's default branch (`origin/main`, or `origin/master` where that's the name) end-to-end — runs the git rebase, auto-resolves conflicts in the project's known auto-generated files, renames branch-added alembic migrations to today's date, regenerates the alembic chain when needed, and re-runs codegen plus the frontend build so generated artifacts reflect the rebased source. Use when the user says "re-main", "rebase on main", or "rebase my branch", or after working on a long-lived feature branch and wanting to pull in main. Full flow when the project has the generated files listed in the skill; otherwise a safe rebase with no auto-resolution.

2026-07-141

updater

teamniteo/claude

Analyzes Renovate PRs to find changelogs, assess codebase impact, and post a summary comment to the PR. Used when asked to review or analyze a Renovate PR.

2026-07-141

port

teamniteo/claude

Port a feature or fix from a PR in a sister project to the current project. Used when copying code between two similar codebases (e.g. two SaaS products that share patterns).

2026-06-041

weekly-commit-sync

teamniteo/claude

Find PRs merged in the last week in a sister project that haven't been ported to this project (and vice versa). Produces a checklist to paste into a tracking issue, then optionally hands off to the port skill.

2026-06-041

name	changelog
description	Generate a weekly changelog entry and prepend it to documentation/changelog.md
argument-hint	<YYYY-MM-DD Monday date, e.g. 2025-03-03>
allowed-tools	["AskUserQuestion","Bash(gh issue view)","Bash(gh pr list)","Bash(gh pr view)","Bash(git )","Edit","Glob","Grep","Read","Skill(demo-video-watcher)"]

Generate a changelog entry for a specific week and prepend it to documentation/changelog.md.

Input

$ARGUMENTS should be a Monday date in YYYY-MM-DD format (e.g. 2025-03-03). If empty, default to the most recent past Monday.

Steps

Parse the date: Determine the Monday date from $ARGUMENTS or calculate the previous Monday.
Confirm with user: Show the target week (Monday to Sunday) and ask the user to confirm before proceeding.

Get commits: Run git log for commits between that Monday 12:00 UTC and the following Monday 12:00 UTC:

git log --oneline --format="%H %s" --after="<monday>T12:00:00Z" --before="<next-monday>T12:00:00Z" origin/main

Filter commits: Keep only commits with feat: or fix: prefixes. Discard chore: and everything else.
Match commits to PRs: For each commit, extract the PR number from (#N) in the commit message. If not found, run gh pr list --search "<sha>" --state merged --json number,title to find the PR.
Read PRs and linked issues: For each PR:
- Run gh pr view <N> --comments to read the PR body and comments
- Extract Refs #N references to find linked issues
- Run gh issue view <N> --comments to read linked issues and their comments
Watch demo videos: If any issue or PR comments contain video attachments, invoke the /demo-video-watcher skill on them to understand what the feature does.
Generate the entry: Create a markdown entry in this format:

## Week of <DD Mon YYYY>

### Features
- **Short title** -- User-facing description.

### Fixes
- **Short title** -- User-facing description.

---

Guidelines for writing entries:

Write from a user's perspective — what changed for them, not implementation details
Keep descriptions to one sentence
NEVER link to GitHub issues or PRs — the changelog is user-facing documentation, not a developer log
Omit the ### Features or ### Fixes section if there are none that week
Sort entries alphabetically by title within each section
If a commit included an update to /documentation, link to the updated documentation page.

Insert the entry: Use the Edit tool to insert the generated entry immediately after the  line in documentation/changelog.md.
Show the result: Display the generated entry to the user for review. Do not commit — let the user decide.