메뉴
Generate a comprehensive summary of AI coding sessions from the past week. Use when the user says "weekly summary", "what did I do this week", "summarize my week", "weekly recap", "week in review", or asks for a summary of recent work across projects.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Load a context primer for the current repo before starting work. Use when the user says "what was I doing here", "catch me up on this repo", "context primer", "what's the open thread", "where did I/we leave off" — and PROACTIVELY when a session opens on work that clearly continues something ("keep going on the refactor", "finish the migration") or when resuming a codebase after a break. Past sessions carry the open thread, prior decisions, and abandoned approaches that code and git history don't show.
Recall what was done on a specific project or topic from past AI coding sessions. Use when the user says "what did I do on [project]", "recall [topic]", "history of [project]", "when did I last work on [thing]" — but also when they reference prior work without asking for history explicitly: "didn't we already fix this", "what was that approach we tried", "why did we do it this way", "what happened to [file/feature]". Use PROACTIVELY before re-deriving a decision or re-solving a problem a past session likely settled — past conversations hold rationale and dead ends that never made it into git.
Show usage metrics and analytics for AI coding sessions. Use when the user asks "how much have I been coding", "session stats", "show me metrics", "tool usage", "which tool do I use most", "active hours", or wants analytics about their AI coding tool usage.
Generate a quick standup summary of yesterday and today's AI coding sessions. Use when the user says "standup", "what did I do yesterday", "daily summary", "what have I been working on", or needs a quick recap for a standup meeting.
| name | weekly-summary |
| description | Generate a comprehensive summary of AI coding sessions from the past week. Use when the user says "weekly summary", "what did I do this week", "summarize my week", "weekly recap", "week in review", or asks for a summary of recent work across projects. |
Generate a weekly summary of the user's AI coding sessions.
Get the date range. Calculate the start date (7 days ago) and end date (today) in YYYY-MM-DD format.
Fetch the digest. Call get_activity_digest with:
startDate: 7 days agoendDate: todaydetail: "highlights" (first + last user messages for substantive sessions)Review the digest. Read the response directly — do NOT send it to a subagent. The highlights mode is compact enough to process inline. For each day, identify:
Drill into key sessions (optional). If any sessions look particularly significant (high message count, interesting topic) but the highlights don't capture enough detail, call get_session_messages on those specific sessions (up to 5) using the filePath from the digest.
Write the summary. Structure it as:
By the numbers: {total sessions} sessions, {total messages} messages across {project count} projects.
Day-by-day: For each day with activity, write 2-4 bullet points capturing the most significant work. Be specific — name projects, features, and outcomes. Skip days with no meaningful activity.
Highlights: The 3-5 most significant accomplishments across the entire week.
Themes: Recurring work streams or focus areas (e.g., "SDK development", "infrastructure", "bug fixes").