Run any Skill in Manus with one click

commit-postmortem-generator

Stars2

Forks0

UpdatedMarch 2, 2026 at 14:20

This skill should be used when the user asks to "analyze fix commits and generate postmortems", "create postmortems from git history", or "summarize bug fixes into postmortem reports".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tizee

tizee/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

More from this repository

same repository

tmux

tizee/skills

Remote control tmux sessions for interactive CLIs by sending keystrokes and scraping output.

2026-07-072

clean-arch

tizee/skills

Review a codebase, PR, or module for requirement fidelity, clean architecture quality, and production robustness. Verifies the change actually implements the stated requirement/user goal before checking structure, distinguishing design-level defects (right code, wrong product) from behavior bugs. Detects cross-layer business logic mixing, dependency direction violations, SOLID problems, module depth issues, information leakage, and KISS/over-engineering smells. Reports findings prioritized with SRE-style severity levels (P0-P3).

2026-07-032

friendly-golang

tizee/skills

Practical guidance for writing, refactoring, and reviewing friendly Go code that is simple, idiomatic, and maintainable. Use whenever working with Go (.go) files, designing Go packages or APIs, structuring a new Go project, reviewing Go code, or refactoring Go modules. Also use when the user mentions goroutines, channels, context, error wrapping, interfaces, go.mod, package layout (cmd/internal/pkg), or Go project structure. Even if the user doesn't say "Go" explicitly, trigger this skill when the context involves .go files or go.mod/go.sum.

2026-07-032

skill-lint

tizee/skills

Validate and lint Agent Skill SKILL.md files and diagnose why a skill fails to load. Use whenever the user wants to check if a skill's frontmatter is valid, find out why a skill "vanished" or is not discovered, lint a single skill, or scan an entire skills directory before committing. Triggers on requests like "validate my skill", "why isn't my skill loading", "check the SKILL.md format", "lint my skills", "diagnose this frontmatter", or any request to verify skill name and description rules. Make sure to use this skill whenever a skill is unexpectedly missing from the available-skills list, since the usual cause is a silent frontmatter parse error rather than a discovery problem.

2026-07-012

system-design-doc

tizee/skills

Write a grounded design/implementation doc for existing code, author a forward-looking design doc before code exists, or apply the embedded principles/checklist to review any design doc. Use whenever the user wants to understand, document, or reverse-engineer how a system, feature, or subsystem is architected (e.g. "how does X work in this repo", "document the Y subsystem", "reverse-engineer Z", "explain the design of W"), or wants to plan and write a new design doc before implementation (e.g. "write a design doc for X", "draft a design for this feature", "I need a design doc to coordinate this work"), or wants design-doc writing principles and a review checklist. Triggers on requests to analyze/document a system's internals, plan a new system's design, or review a design doc for completeness. Output follows a house format: prose + ASCII/Unicode/mermaid flowcharts, a key-file index, behavioral contracts, and a BDD scenario table, validated against checklist.md.

2026-07-012

reverse-crack-poc

tizee/skills

Guide a reverse-engineering proof-of-concept on a macOS crackme / license-check binary, for learning and interview preparation. Use this whenever the user is analyzing a app's authorization / license-gating module and wants to reconstruct its gating model, call chain, architecture differences (arm64 / x86_64 / universal Mach-O), and validate a minimal binary patch with LLDB and code signing. Trigger on mentions of crackme, license-check PoC, Mach-O / IDA / LLDB / objc_msgSend analysis, "find the gating branch", patch validation, universal binary slices, keygen-me vs patch-me, or CTF-style binary patching — even when the user does not say the word "skill".

2026-06-212

name	commit-postmortem-generator
description	This skill should be used when the user asks to "analyze fix commits and generate postmortems", "create postmortems from git history", or "summarize bug fixes into postmortem reports".
version	0.1.0

Commit Postmortem Generator

Core Purpose

Analyze fix commits in a git repository and generate concise postmortem reports that capture critical information about bugs and their fixes.

Basic Workflow

To generate postmortems:

Fetch the latest N fix commits (default: 100)
Group commits by related issues
Generate markdown postmortem reports with key details
Store reports in ./.postmortem/ directory

Usage

When the user doesn't specify a number of commits

Prompt the user: "How many latest fix commits would you like to analyze?"
Use their response to run the script:

./scripts/generate-postmortems.sh -c [user-specified-number]

When the user specifies a number

# Example: Analyze 50 commits
./scripts/generate-postmortems.sh -c 50

# With custom output directory
./scripts/generate-postmortems.sh -c 50 -o ./my-postmortems/

Resources

references/postmortem-template.md - Minimal postmortem template
scripts/generate-postmortems.sh - Main script to generate postmortems