All authors
Claude Skills by leonardo-amaral-3
github.com/leonardo-amaral-314 skills0 installs0 views
- DiarioSave or enrich this session's note in the Obsidian vault of the current workspace (`<workspace>/claude/diario`) — a summary of what was done and decided, links to artifacts/PRs/cards/planning files, open items and how to resume the session. Use when the user asks to save the session to Obsidian ("salva no obsidian", "registra essa sessão") or when wrapping up significant work.Votes: 0GitHub stars: 2
- Gm CardQualify demand into a direction card on the team board (the team board declared in the workspace CLAUDE.md) — either creating it from a one-line direction, or promoting an issue that gm-triage left in Triagem. Captures current state with evidence, desired direction, motivation and MANDATORY acceptance criteria (gate G1), using the right template per type (bug vs melhoria vs débito), and suggests the route (completa/curta). Use right after a gm-explore or a gm-triage, or whenever registering d...Votes: 0GitHub stars: 2
- Gm CorrecaoTurn the CI review's parecer on a PR into decisions on the record - every finding verified against the spec, then fixed, refuted, or promoted to a card, with a reply on each inline comment. Use after the review workflow posts its findings on a PR that is already in code review, before handing the PR to a human validator.Votes: 0GitHub stars: 2
- Gm ExploreExploratory, read-only investigation of how something currently works in the codebase. Use when the user wants to understand the current state of a behavior, rule, or flow ("how is X today?", "can a user do Y?") before deciding whether it should change. Checks the team board for existing cards on the topic, answers with file:line evidence, never proposes or implements solutions, and — when the question came from a ❓ Dúvida card — publishes the finding on it and closes it as answered knowledge.Votes: 0GitHub stars: 2
- Gm HotfixDrive a real S1 production emergency — faturamento parado or corrupted data — down the expedite rail on the team board (the team board declared in the workspace CLAUDE.md). Proves the S1 criterion and the one-at-a-time limit, opens a minimal card carrying repro + risk + the verification query, branches release/hotfix-* from main (never from dev), implements with tests, opens the PR to main with mandatory AI + human review, runs the BLOCKING post-deploy verification, tags, back-merges into dev...Votes: 0GitHub stars: 2
- Gm ImplementExecute the next pending task of a planned feature - right branch in the right repo (created linked to the card via Development field), task file as the prompt, tests run BEFORE presenting, risk-ranked summary, commit only after explicit approval, deviation protocol when reality contradicts the spec. Use after gm-plan-tasks, once per task, preferably in a fresh session.Votes: 0GitHub stars: 2
- Gm Plan TasksBreak a spec into ordered, independent implementation tasks — each task file is the complete prompt for a fresh agent. Proposes the whole breakdown at once for the user to veto/adjust; enforces the 6-8 task ceiling; mirrors the task list on the card. Use after gm-spec, before /gm-implement.Votes: 0GitHub stars: 2
- Gm PrdCreate a Product Requirements Document (PRD) through deep conversational Q&A, seeded by a board card when one exists. Use when a card is picked up for implementation, or when planning any feature that needs clear requirements before coding. Writes planning/<folder>/PRD.md and publishes the PRD as a comment on the card so downstream steps (tech spec, CI review) can find it on GitHub.Votes: 0GitHub stars: 2
- Gm ReleaseCut the release train from the team board (the team board declared in the workspace CLAUDE.md) — read the validated queue (🚂 Release, plus cards closed while in 🧪 Validação em Dev), reconcile it against what is actually merged in dev, classify the train as trivial or sensitive (migrations / data treatment), open the dev→main PR, tag with calver, publish dual release notes, run the BLOCKING post-deploy verification for sensitive cards, move the cards to ✅ Produção and produce the list of req...Votes: 0GitHub stars: 2
- Gm ShipClose the implementation loop - verify every task complete, run the full suite, push, open the PR carrying the acceptance-criteria contract and the dev-validation checklist, referencing the board card, and move the card to code review. Use after the last gm-implement task is approved and committed.Votes: 0GitHub stars: 2
- Gm SpecCreate the single specification (requirements + technical) for a board card — the contract that makes AI implementation safe. Seeded by the card, built through codebase exploration and focused Q&A, hardened by an adversarial critique, and gated by explicit human approval. Publishes the spec as a comment on the card. Replaces the old gm-prd + gm-tech-spec pair as the default path (gm-prd remains only for genuinely new product areas).Votes: 0GitHub stars: 2
- Gm Tech SpecDEPRECATED - superseded by gm-spec, which fuses requirements + technical specification into a single document with adversarial critique and a human approval gate. Use /gm-spec instead.Votes: 0GitHub stars: 2
- Gm TriageTurn a raw report — a hospital's message, a stack trace, a loose idea — into qualified demand at the door of the team board (the team board declared in the workspace CLAUDE.md). Classifies type/severity/class/module with written criteria, deduplicates against open and closed issues before creating anything, fills the template for the type, records origin and requester, and parks the card in 📥 Triagem. Also routes away what is not demand. Use whenever something arrives from outside the board,...Votes: 0GitHub stars: 2
- MapearGera ou atualiza o mapa de arquitetura de um repo/módulo do workspace atual em `<workspace>/claude/mapas/`, indexado pelo brain MCP. Use quando o usuário pedir "/mapear <repo>", "mapeia o <repo>", ou após mudanças estruturais grandes num repo (novo módulo, pasta reorganizada, integração nova).Votes: 0GitHub stars: 2