Menu
Summarize the day's work and put it in context
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Structured brainstorming for exploring new features or solving complex problems
Scope, architect, and plan new tasks
Multi-angle code review before merging
Wrap up work — atomic commits and push to origin
Full end-to-end (E2E) testing skill utilizing the browser. Make sure to use this skill whenever the user asks to "test the app", "run end to end tests", "verify the UI", "check if the app works", or wants you to use the browser to interact with and test the application flow. This skill orchestrates creating a test plan, getting user approval, navigating the application using the browser, independently fixing obstacles, and generating a progressive test report.
Analyzes the current project repository and workflows to provide a high-level status report. Use this skill when the user asks for a status update, wants to know "what's next", asks where development left off, or needs a summary of recent work to regain context. Do NOT use this skill if the user is asking you to actually implement the next feature, commit code, or search the codebase for specific files.
Baseado na classificação ocupacional SOC
| name | stats |
| description | Summarize the day's work and put it in context |
Summarize the day's engineering work and provide perspective on progress.
At the end of a work day, or when the user asks for a status check.
Gather raw data. Collect from all relevant repos:
git log --oneline --since="midnight" --author="$(git config user.name)" — today's commitsgit diff --stat HEAD~<n>..HEAD — scope of changes (files, insertions, deletions)Categorize the work. Group today's contributions by type:
Summarize achievements. Write a concise narrative of what was accomplished, focusing on outcomes over activities. Lead with impact: what changed for the user, the product, or the codebase.
Quantify the session. Present key metrics:
| Metric | Value |
|---|---|
| Commits | count |
| Files changed | count |
| Lines added / removed | +X / -Y |
| Conversations | count |
| Solutions documented | count (if any) |
Contextualize. Put today's work in broader perspective:
Carry-forward items. List anything that should be picked up next:
Present the summary. Format as a clean, scannable report using the template below.
# Daily Summary — [YYYY-MM-DD]
## What Got Done
[Concise narrative of accomplishments, 2-4 sentences]
## Breakdown
### 🚀 Features
- [item]
### 🐛 Fixes
- [item]
### 🔧 Refactors / Infra
- [item]
## By the Numbers
| Metric | Value |
|--------|-------|
| Commits | X |
| Files changed | X |
| Lines | +X / -Y |
## Carry Forward
- [ ] [item to pick up next]