Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

mu-retro

Estrelas2

Forks0

Atualizado6 de maio de 2026 às 15:52

Use for weekly or periodic retrospective — gather git metrics, review patterns, capture learnings to Claude Code memory.

Instalação

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ê.

Executar no Manus

Fonte

knotmark-ai

knotmark-ai/devmuse

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

SKILL.md

readonly

name	mu-retro
description	Use for weekly or periodic retrospective — gather git metrics, review patterns, capture learnings to Claude Code memory.

Retrospective

Gather quantitative git metrics and qualitative reflections for a time period. Capture non-obvious learnings to Claude Code memory for future sessions.

Independent of the main pipeline. Invoke with /mu-retro or /mu-retro 14d.

Process Flow

digraph mu_retro {
    "Parse time window\n(default: 7d)" [shape=box];
    "Gather git data\n(parallel)" [shape=box];
    "Zero commits?" [shape=diamond];
    "Report: No activity" [shape=box];
    "Generate metrics table\n+ per-author breakdown" [shape=box];
    "Qualitative reflection\n(dialogue with user)" [shape=box];
    "Write retro artifact\n+ commit" [shape=box];
    "Write to Claude Code memory\n(non-obvious findings only)" [shape=doublecircle];

    "Parse time window\n(default: 7d)" -> "Gather git data\n(parallel)";
    "Gather git data\n(parallel)" -> "Zero commits?";
    "Zero commits?" -> "Report: No activity" [label="yes"];
    "Zero commits?" -> "Generate metrics table\n+ per-author breakdown" [label="no"];
    "Report: No activity" -> "Qualitative reflection\n(dialogue with user)";
    "Generate metrics table\n+ per-author breakdown" -> "Qualitative reflection\n(dialogue with user)";
    "Qualitative reflection\n(dialogue with user)" -> "Write retro artifact\n+ commit";
    "Write retro artifact\n+ commit" -> "Write to Claude Code memory\n(non-obvious findings only)";
}

Process

Parse time window from argument (default: 7d)
- Convert to absolute start date at midnight
- Example: 7d on 2026-04-12 → start 2026-04-05T00:00:00
Gather data (run in parallel):

# Commits in window
git log --since="<date>" --format="%H|%an|%s|%aI"

# Author summary
git shortlog -sn --since="<date>"

# File change stats
git log --since="<date>" --name-only --format="" | sort | uniq -c | sort -rn | head -10

# Test file count
find . -name "*test*" -o -name "*spec*" | grep -v node_modules | wc -l

Check for zero commits:
- If no commits in window → report "No activity in this period"
- Skip metrics table, proceed directly to qualitative reflection
Generate metrics table:

Metric	Value
Commits	N
Contributors	N
Lines changed	+N / -M
Test files	N
Hottest files	top 3 by change frequency

Per-author breakdown:

Author	Commits	Top area
...	...	...

Qualitative reflection (dialogue with user, one at a time):
- "What went best this period?"
- "What was most surprising?"
- "What would you change next period?"
Write retro artifact to docs/retro/YYYY-MM-DD-retro.md
Commit artifact
Write to Claude Code memory (project type):
- Only non-obvious findings worth remembering across sessions
- Examples: "module X is a change hotspot", "test coverage thin in Y area"
- Check existing memory first — update if similar memory exists, create new if not

Key Principles

Data first, then reflection — show the numbers before asking opinion
One reflection question at a time — don't overwhelm
Memory is selective — only write non-obvious, durable findings. Don't dump metrics.
Handle edge cases gracefully — zero commits, shallow clones, monorepos
Standalone, no chaining — does NOT invoke other skills

Mais deste repositório

mesmo repositório

mu-review

knotmark-ai/devmuse

Use when code changes need review, verification, and integration - covers review dispatch, feedback handling, verification gates, and merge/PR workflow

2026-05-212

mu-arch

knotmark-ai/devmuse

Use before any creative engineering work to design technical architecture — components, interfaces, data flow, error handling. For product/UX requirements (user flows, feature specs), use mu-prd first.

2026-05-112

mu-wiki

knotmark-ai/devmuse

Use when user wants to generate or maintain project-level architecture documentation. Two modes: generate (full wiki creation from codebase analysis) and update (incremental maintenance via git diff). On-demand only — never auto-routed by mu-route.

2026-05-112

mu-route

knotmark-ai/devmuse

Use at the start of any unprefixed user message within DevMuse's domain (dev or product work) to route to the right skill. Confidence-based: high confidence invokes silently, medium gives a one-line proposal, low gives full proposal with override options. Bypassed by direct slash invocations (`/mu-<skill>`).

2026-05-112

mu-write-skill

knotmark-ai/devmuse

Use when creating new skills, editing existing skills, or verifying skills work before deployment

2026-05-082

mu-biz

knotmark-ai/devmuse

Use when validating a business premise or defining product strategy (market, BMC, VPC, personas, MVP scope). Two modes: quick (4 forcing questions) or full (comprehensive analysis).

2026-05-062

Retrospective

Gather quantitative git metrics and qualitative reflections for a time period. Capture non-obvious learnings to Claude Code memory for future sessions.

Independent of the main pipeline. Invoke with /mu-retro or /mu-retro 14d.

Process Flow

digraph mu_retro { "Parse time window\n(default: 7d)" [shape=box]; "Gather git data\n(parallel)" [shape=box]; "Zero commits?" [shape=diamond]; "Report: No activity" [shape=box]; "Generate metrics table\n+ per-author breakdown" [shape=box]; "Qualitative reflection\n(dialogue with user)" [shape=box]; "Write retro artifact\n+ commit" [shape=box]; "Write to Claude Code memory\n(non-obvious findings only)" [shape=doublecircle]; "Parse time window\n(default: 7d)" -> "Gather git data\n(parallel)"; "Gather git data\n(parallel)" -> "Zero commits?"; "Zero commits?" -> "Report: No activity" [label="yes"]; "Zero commits?" -> "Generate metrics table\n+ per-author breakdown" [label="no"]; "Report: No activity" -> "Qualitative reflection\n(dialogue with user)"; "Generate metrics table\n+ per-author breakdown" -> "Qualitative reflection\n(dialogue with user)"; "Qualitative reflection\n(dialogue with user)" -> "Write retro artifact\n+ commit"; "Write retro artifact\n+ commit" -> "Write to Claude Code memory\n(non-obvious findings only)"; }

Process

Parse time window from argument (default: 7d)

Convert to absolute start date at midnight
Example: 7d on 2026-04-12 → start 2026-04-05T00:00:00

Gather data (run in parallel):

Check for zero commits:

If no commits in window → report "No activity in this period"
Skip metrics table, proceed directly to qualitative reflection

Generate metrics table:

Metric

Value

Commits

Contributors

Lines changed

+N / -M

Test files

Hottest files

top 3 by change frequency

Per-author breakdown:

Author

Commits

Top area

...

Qualitative reflection (dialogue with user, one at a time):

"What went best this period?"
"What was most surprising?"
"What would you change next period?"

Write retro artifact to docs/retro/YYYY-MM-DD-retro.md

Commit artifact

Write to Claude Code memory (project type):

Only non-obvious findings worth remembering across sessions
Examples: "module X is a change hotspot", "test coverage thin in Y area"
Check existing memory first — update if similar memory exists, create new if not

Key Principles

Data first, then reflection — show the numbers before asking opinion

One reflection question at a time — don't overwhelm

Memory is selective — only write non-obvious, durable findings. Don't dump metrics.

Handle edge cases gracefully — zero commits, shallow clones, monorepos

Standalone, no chaining — does NOT invoke other skills