Menu
Summarize unread Slack threads from key channels, highlight action items
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
Analyze, group, and commit uncommitted changes as atomic conventional commits. Use this skill whenever the user says 'commit', 'commit this', 'commit these changes', 'commit my changes', 'smart commit', wants their diff split into logical commits, or asks to create a commit in any way. Always use this skill for committing — never run git commit directly.
Audit Claude Code configuration for security: check permissions, hooks, MCP servers, and settings
Create or update today's daily note at `~/knowledge/notes/journal/YYYY/MM-MMM/YYYY-MM-DD-DayName.md`, appending or replacing a session entry under `## Agent Summary`. Use when the user asks to update the daily note, log a session, append to the journal, or when invoked by the session-history hook after a session summary is written.
Edit config files inside the stow-based dotfiles repo and re-stow them with `make link`. Use this skill whenever the user asks to modify, add, or tweak any config under `$HOME` that lives in dotfiles — `.zshrc`, `.zshenv`, `.zprofile`, anything under `.config/`, `.local/`, `.claude/`, `.kiro/`, `.meshclaw/`, `.aws/`, `.unison/`, the `Makefile`, or any other tracked dotfile. Trigger even if the user phrases it as "change my config", "update my zshrc", "add this to claude settings", "tweak my tmux config", "modify my aliases", etc. — direct edits to `$HOME` are wrong because they bypass version control and get clobbered by the next `make link`.
Summarize unread emails via Outlook MCP, group by priority, draft replies
Audit IAM policies in CDK/CloudFormation/Terraform for least-privilege violations
| name | slack-catchup |
| description | Summarize unread Slack threads from key channels, highlight action items |
When asked to catch up on Slack, summarize channels, or used via /loop:
Identify channels — Check configured channels of interest. Common security team channels:
Fetch recent messages — Use the Slack MCP server to:
Identify action items — Look for:
Summarize threads — For each active thread:
Generate catchup — Produce a prioritized summary.
# Slack Catchup — [Date/Time]
## Action Items (X items)
- **#oncall**: @you was mentioned — [person] needs help with [issue]
- **#team**: Review requested on [topic] by EOD
## Active Discussions
- **#security-announcements**: New policy change — TL;DR: SLA for critical issues reduced to 7 days
- **#team**: Discussion about [topic] — 12 messages, concluded with [decision]
## FYI
- **#general**: All-hands moved to Thursday
Recommended: /loop 2-3x daily or on-demand after meetings