메뉴
Generate a weekly changelog entry and prepend it to documentation/changelog.md
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
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.
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).
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.
| 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.
$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.
$ARGUMENTS or calculate the previous Monday.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
feat: or fix: prefixes. Discard chore: and everything else.(#N) in the commit message. If not found, run gh pr list --search "<sha>" --state merged --json number,title to find the PR.gh pr view <N> --comments to read the PR body and commentsRefs #N references to find linked issuesgh issue view <N> --comments to read linked issues and their comments/demo-video-watcher skill on them to understand what the feature does.## Week of <DD Mon YYYY>
### Features
- **Short title** -- User-facing description.
### Fixes
- **Short title** -- User-facing description.
---
Guidelines for writing entries:
### Features or ### Fixes section if there are none that week<!-- changelog-insert-marker --> line in documentation/changelog.md.