Project Rounds
Bunz80/claude-project-rounds
Continuidade de sessão e contexto para projetos longos com Claude
Ver no GitHubSkill para Claude Code que mantém continuidade de sessão em projetos longos através de logs de trabalho numerados e changelog centralizado. Permite recuperar contexto completo em 30 segundos quando uma nova sessão inicia, sem perder o fio da meada entre encerramentos.
Instalação
npx convez-ai Bunz80/claude-project-rounds1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerenciar múltiplos projetos/clientes em paralelo sem perder progresso
- Trabalhar em iniciativas longas (refatorações, migrações, campanhas SEO)
- Colaboração onde outro membro ou sessão futura precisa retomar o trabalho
- Manter histórico rastreável de mudanças por projeto
Veredito

Solução prática e bem-pensada para o problema real de perda de contexto em projetos longos com Claude. A abordagem baseada em convenção de diretórios é agnóstica de domínio e funciona tanto para dev quanto para conteúdo, operações ou pesquisa — recomendada para quem trabalha com múltiplos projetos simultâneos.
README
A tradução para o português deste README ainda está na fila.
project-rounds
A Claude Code skill that gives any project session continuity across multiple Claude sessions.
Don't lose the thread when the session resets.
What it does
After every significant intervention, the skill ensures:
- A per-project work log (
work/<item>.md) gets a new Round entry with what was done. - A central
work/CHANGELOG.mdgets a dated bullet that indexes the per-project entry.
When a new Claude session starts, reading those two files restores full context in 30 seconds.
Why
If you've ever closed Claude Code, opened it the next day, and lost the thread of where you were on a long-running project — this skill prevents that.
Especially useful when:
- Managing multiple projects / clients / sites in parallel
- Working on long initiatives (refactors, migrations, SEO campaigns, content production, infrastructure builds)
- Collaborating where another session (yours, tomorrow's, or a colleague's Claude) needs to pick up where you left off
Install
Globally (all your Claude Code projects)
git clone https://github.com/Bunz80/claude-project-rounds.git ~/.claude/skills/project-rounds
The skill becomes available in any session on your machine.
Per-project only
cd <your-project>
git clone https://github.com/Bunz80/claude-project-rounds.git .claude/skills/project-rounds
How it works
The skill defines a convention:
<project-root>/
├── work/
│ ├── CHANGELOG.md ← cross-project index, reverse-chrono
│ ├── itemA.md ← per-item log with numbered Rounds
│ ├── itemB.md
│ └── ...
When Claude detects a tracked item by name, it reads work/<item>.md to set context. When work is done, it appends to both files before closing the session.
Templates
templates/work-log-template.md — boilerplate for a new work/<item>.md
templates/changelog-entry-template.md — examples of well-formed CHANGELOG entries
templates/examples/seo-example/ — real-world example of using the system for SEO across multiple sites (with schema snippets, IndexNow patterns)
Domain-agnostic
The skill is intentionally generic. Works equally for:
- Software development projects (feature branches, refactors, migrations)
- SEO / content / digital marketing (multi-site management)
- Operations / infrastructure (deploys, server changes, incidents)
- Research / writing (drafts, revisions, fact-checks)
- Client work (multi-client billing-tracked work)
Anything where you want a Claude-readable history.
License
MIT — fork it, ship it.
Contributing
PR welcome. If you've evolved the pattern (team-shared CHANGELOG, CI integration, anti-patterns), open an issue or PR.