convez.ai
SkillAutomaçãoAvançado
jtgp-solutions

JTGP Claude Code Toolkit

jtgp-solutions/jtgp-cc-toolkit

Specs permanentes, sessões descartáveis: toolkit CLI para engenharia autônoma escalável

Ver no GitHub
InicialPluginScore · de 0 a 100

Um marketplace privado de plugins que padroniza desenvolvimento ancorado em specs, com workflows autônomos e multi-contexto. A toolkit oferece 10 comandos CLI integrados a agentes (Opus e Sonnet), hooks git e suporte a múltiplas issue trackers, knowledge bases e linguagens — tudo configurável por engagement em um arquivo `.jtgp/config.json` que nunca é commitado.

Instalação

$npx convez-ai jtgp-solutions/jtgp-cc-toolkit

1 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

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 2 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Padronizar workflows de desenvolvimento em múltiplas engagarias/projetos
  • Implementação autônoma com quality gates e verificação de evidências antes de PRs
  • Resumir contexto completo em novas sessões usando specs e contextos versionados
  • Revisar PRs de colegas em worktrees isoladas com crítica adversarial

Veredito

Ferramenta sofisticada para times que precisam de reproducibilidade e autonomia em implementação de código, com suporte robusto a múltiplos contextos corporativos. Exige investimento inicial em configuração mas entrega padronização durável através de specs versionadas, não sessões descartáveis.

README

A tradução para o português deste README ainda está na fila.

JTGP Claude Code Toolkit

A private, versioned plugin marketplace that standardizes spec-anchored development across multiple engineering engagements. Adapts to any engagement via interactive setup — install once, configure per workspace.

Core idea

Sessions are disposable. Specs are permanent.

Context lives in files, not in a chat session. A living SPEC.md per issue is the source of truth — created before planning, kept current through implementation, synced to your knowledge base (Outline/Notion) if configured.

Setup

Install the plugin, then run setup once per engagement workspace:

/plugin marketplace add jtgp-solutions/jtgp-cc-toolkit
/plugin install jtgp-core@jtgp
/jtgp:setup

Setup asks 22 questions covering: issue tracker, knowledge base, PR tool, language preferences (code, docs, terminal, commits, PR descriptions), code standards, test framework, branch conventions. All answers are saved to .jtgp/config.json (git-ignored, stays local).

The workflow

/jtgp:setup          → configure the engagement (once)
/jtgp:spec ISSUE-ID  → create the living spec (source of truth)
/jtgp:plan ISSUE-ID  → phased implementation plan from the spec
/jtgp:critique       → adversarial loop hardens the plan
/jtgp:execute        → autonomous implementation (stops at PR boundary)
/jtgp:verify         → evidence gate: PASS / CONCERNS / FAIL / WAIVED
                     → PR opened by human after PASS

Plus:

/jtgp:resume ISSUE-ID  → rebuild full context in a fresh session
/jtgp:review-pr N      → review a colleague's PR (isolated worktree)
/jtgp:learn            → capture a correction as a permanent rule
/jtgp:cleanup          → remove orphaned worktrees and stale branches

What adapts per engagement

Everything in .jtgp/config.json:

CategoryFields
Identityengagement name, git email
Issue trackergithub / gitlab / jira / notion / linear / manual
Knowledge baseoutline / notion / confluence / none
PR toolgh / glab / manual
Languagescode, docs, terminal, commits, PR descriptions, PR reviews
Code standardsno-comments rule, code style, test framework, build tool
Conventionsbranch pattern, commit convention

Multi-engagement example

workspace/project1/    → /jtgp:setup → github + outline + gh + pt-br docs + java-spring
workspace/project2/     → /jtgp:setup → gitlab + outline + glab + pt-br docs + java-spring
workspace/project3/     → /jtgp:setup → notion + notion  + gh  + pt-br docs + react-ts
workspace/new-project/    → /jtgp:setup → any combination

Components

  • skills/ — 10 workflow commands namespaced /jtgp:*
  • agents/ — planner, critic, developer, tester, investigator, quality-gate (Opus for reasoning, Sonnet for execution)
  • hooks/ — git identity guard (reads from config), no-comments guard (respects config), spec-sync reminder
  • lib/ — context.sh loads config into env vars for hooks
  • templates/ — SPEC.md, CONTEXT.md, config.json

Security

.jtgp/config.json is always git-ignored. It contains your corporate email and engagement-specific IDs — it must never be committed.

Ver o original no GitHub

Bom para

Relacionados