Menu
Capture session activity into a daily log file in logs/ for later review.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | session-log |
| description | Capture session activity into a daily log file in logs/ for later review. |
| user_invocable | true |
Capture what was done in this session and append it to today's daily log at logs/YYYY-MM-DD.md. This is a personal activity log - quick, factual, and scannable - so you can rewind what you did on any given day.
Collect information from the session:
git diff --stat and git log --oneline -10 to see what files changed and recent commitsdate '+%H:%M' for the entry timestamp and date '+%Y-%m-%d' for the filenameDetermine the log file path: logs/YYYY-MM-DD.md (e.g., logs/2026-04-14.md).
If the file does not exist, create it with a top-level heading:
# YYYY-MM-DD
Append a new entry to the file. Each entry follows this format:
## HH:MM - Brief one-line description of the work
- What was done (2-5 bullet points, concise)
- Key files created or modified
- Related issues, PRs, or context if any
After writing, report the entry you added in one line. Do not read the file back.
/session-distill from here - they are independent skills and may both be triggered by the same hook.Create or update a GitHub PR for the current branch. It handles branch creation from main, rebases the full branch chain up to main, pushes with --force-with-lease, and generates a PR with a smart title and description focused on business rules and architecture changes. It can also screenshot the affected UI if the change touches frontend code.
Implement features and bugfixes using strict outside-in TDD. Each cycle traces back to requirements and design docs when available. It includes a deliberate refactoring phase and generates integration tests when a vertical slice is complete. It wires up BDD step definitions when feature files exist. It can receive a Linear issue as input, rebuilds docs (requirements, design, plan) from the issue into the repo before coding, and graduates them into permanent knowledge after the implementation is complete.
Create an implementation plan for an initiative. It references specific requirements and design decisions from docs/requirements/ and docs/design/, produces a plan in docs/plans/, and generates test cases traced back to requirements. It bridges "what to build" and "building it."
Record a "before/after" walkthrough video pair for a PR using Playwright. Trigger when the user asks to record a PR video, demo a fix, capture a UI walkthrough, or produce reviewer-facing media for a frontend or workflow change. Produces narrated mp4 (preferred for browser drag-drop into a PR description) and gif (committable to the repo so no browser is needed). Follows the team visual standard.
Split requirements, design specs, and plans into self-contained Linear issues targeting ~200-300 LOC each. It reads from the project's docs/requirements/, docs/design/, and docs/plans/, creates issues with the full spec embedded in the body, tags them with "agent issue", and creates an epic parent issue when more than two issues are generated. It deletes the repo docs files after the issues are created.
Review a PR or diff for architectural quality - SOLID principles, codebase consistency, dependency direction, error handling, data flow, test architecture, performance, and security. It reads the code review output for context, checks alignment with design docs, and produces actionable findings for the coding agent to fix.