agentleFS
sennaBrunosennaBruno/claude-skills/skills/obsidian-review/SKILL.md

review

Skill1 starsChanged 8 months agoApache-2.0View on GitHub

Use when the user wants to review the current state of a specific project, check progress, identify blockers, or get a status summary with next steps

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • +3 more from dzhng
  • +5 more from Lambenthan

The file

Files
SKILL.md

Review — Status de Projeto

Overview

Resume o estado atual de um projeto especifico, cruzando documentacao do vault com estado real do codigo-fonte. Gera snapshot honesto de progresso, blockers e proximos passos.

Workflow

1. Identificar Projeto

Resolver argumento do usuario para projeto:

Input (case-insensitive)ProjetoRepo Path
zapflow, zap, alinhou, barberZapFlow/home/senna/whatsapp-saas
scrap, furnace, jogo, gameScrap Furnace/home/senna/scrap-furnace
anime, animerec, recAnimeRec/home/senna/animerec
crypto, arb, cryptoarbCryptoArb/home/senna/cryptoarb
remember, adhd, lembreteAlways Remember/home/senna/always-remember
market, bot, marketplaceMarketBot (arquivo)/home/senna/marketplace-bot

Se input nao reconhecido, listar projetos disponiveis e perguntar.

2. Coletar Dados (paralelo)

FonteComando/PathInfo
Contexto vault01 - Projetos/[X]/\_contexto.mdArquitetura, status documentado
Git loggit log --oneline -20 no repoAtividade recente
Git statusgit status no repoChanges pendentes
Branchesgit branch no repoTrabalho em paralelo
Design docsdocs/plans/ no repoPlano original, fases
Notas vault07 - Claude/*[projeto]*Analises anteriores
TestsRunner do projeto (pytest/vitest)Estado dos testes

3. Output

Criar nota em /mnt/c/Users/senna/ObsidianVault/07 - Claude/YYYY-MM-DD-review-[projeto-slug].md:

---
tags:
  - analise
  - projeto/[tag]
date: YYYY-MM-DD
---

# Review — [Projeto] — YYYY-MM-DD

## Status Geral
[1-2 frases: fase atual, saude do projeto, momentum]

## Ultimo Progresso
[Baseado em git log — ultimos commits relevantes]

## O Que Esta Funcionando
[Features/sistemas completos e funcionais]

## Blockers / Riscos
[O que impede progresso — ser honesto, nao suavizar]

## Divida Tecnica
[Se identificada no codigo ou docs]

## Proximos Passos
1. [Mais urgente]
2. [Segundo mais urgente]
3. [Desejavel]

## Metricas
| Metrica | Valor |
|---------|-------|
| Commits (30d) | X |
| Tests | X passing |
| Fase atual | X de Y |
| Ultimo commit | YYYY-MM-DD |

Regras

  • NUNCA escrever fora de 07 - Claude/
  • Ser honesto sobre blockers — transparencia > otimismo
  • Se projeto esta em 04 - Arquivo/, mencionar que esta arquivado e o motivo
  • Incluir metricas concretas sempre que possivel
  • Se testes falhando, reportar quais e por que
  • Usar wikilinks para referenciar notas e projetos
  • Nao rodar testes automaticamente sem confirmacao do usuario (podem ser lentos)
  • Idioma: Portugues BR

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.