- Skills
- 14
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 4
Nicolas Gentile 的 Skills 14
incident-postmortem
Writes a blameless incident postmortem (timeline, impact, root cause, contributing factors, action items) from logs, chat history or notes. Use after an outage, a failed deploy or a production bug, or when asked for an "incident report" or "postmortem".
release-notes
Writes user-facing release notes and a changelog entry from merged PRs or commits since the last release. Use when asked for "release notes", a "changelog" or "what changed since vX".
technical-docs
Writes technical documentation, specs and design docs (context, goals, ADR-style decisions, mermaid diagrams, rollout plan) and suggests where to store them. Use when asked to "document this", for a design doc, a spec, an ADR, a technical proposal or an architecture README.
status-report
Builds a status report (weekly or for a period) by combining git history, the task tracker and hub memory; returns done / in progress / blockers / next steps. Use when asked for a status report, a weekly, "what did I do this week", a standup summary or an update for a manager.
review-pr
Reviews a pull request with a fixed checklist (correctness, security, tests, readability) and returns prioritized findings. Use when asked to review a PR, a diff or a code change.
memory-capture
Decides what is worth remembering from the conversation and saves it as short, self-contained notes with [[links]] to people, companies and projects. Use when the user says "remember this", "save this", "note that", or at the end of a session with decisions worth keeping.
meeting-notes
Turns a meeting transcript or rough notes into a summary with decisions, action items (owner + date) and open questions, and saves the durable parts to memory. Use when the user pastes a transcript, call notes or says "summarise this meeting".
debug-error
Systematic debugging of an error or bug - reproduce, read logs and error tracking, form hypotheses, minimal fix, regression test, and save the lesson to memory. Use when given a stack trace, an error message, a failing test, an error-tracker alert, or "this doesn't work".
weekly-review
Guides a short personal weekly review (what got done, what slipped, priorities for next week) using what memory already knows, and saves the outcome. Use when the user says "weekly review", "plan my week" or "how did my week go".
fixture-work
Solo work
fixture-work-compartida-side
De work, compartida con side
fixture-side
Solo side
fixture-compartida
Skill visible en todos los contextos
fixture-personal
Solo personal