Techne – Skills para Higiene de Repositórios
ajbarea/techne
Audit builds, tame CI, sync docs, keep sister repos in lockstep
Ver no GitHubConjunto de 9 skills Claude para fluxos multi-repositório que audita builds, domina CI/CD, sincroniza docs↔código e mantém repositórios irmãos em sincronia. Executáveis como plugin único, com foco em convenções opinionadas e artefatos intermediários para revisão humana antes de mutações.
Instalação
npx convez-ai ajbarea/techne1 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
- Auditar execuções de make targets contra logs históricos e detectar regressões
- Validar documentação técnica contra implementação real (CLI, paths, assinaturas)
- Controlar deriva entre repositórios relacionados em tempo real
- Planejar commits estruturados via COMMITS.md antes de efetivamente fazer push
- Flagear e corrigir ruído em workflows de GitHub Actions
Veredito

Skill robusto e maduro para times que já usam Claude Code em fluxos multi-repo. Requer adesão a convenções (Makefile, logs/dev-*.log, .claude/skill-context.md) mas compensa com automação profunda de tarefas de higiene que manualmente consumem horas. Ideal para projetos complexos com múltiplos repositórios relacionados.
README
A tradução para o português deste README ainda está na fila.
techne
Opinionated Claude Code skills for repo hygiene: audit builds, tame CI noise, hunt doc/code drift, keep linked repos in lockstep. Installable as a single /plugin.
/plugin marketplace add ajbarea/techne
/plugin install techne@techne
What's in the box
| Skill | What it does |
|---|---|
techne:audit | Runs the repo's make targets in dependency order and reconciles terminal output against logs/dev-*.log archives. |
techne:auto-commit | Groups working-tree changes into a structured COMMITS.md plan for staged review before anything lands. |
techne:ci-audit | Audits GitHub Actions runs on the current branch/PR: surfaces warnings, failures, and noise; fixes what's fixable in-repo. |
techne:deslop | Scans comments and docstrings for AI-generated slop and proposes tightened rewrites. |
techne:docs-site | Maintains the Zensical-powered docs site: config, deploy pipeline, theming, link integrity. |
techne:docsync | Verifies documentation claims (CLI commands, paths, config keys, signatures) against the actual code. |
techne:research-grounded | Flags design decisions in IMPL/ROADMAP that lack # research(YYYY-MM): provenance, then web-searches to ground them. |
techne:reslop | Rewrites docstrings grounded in the implementation rather than deleting them outright. |
techne:sisters | Cross-repo drift audit across the sister repos listed in ~/.claude/techne.toml. |
techne:theoros | Starts an observed live dev session: Claude drives the REPL in a named tmux session; you spectate read-only via tmux attach -r. |
Install
Add the marketplace and install the plugin from inside Claude Code:
/plugin marketplace add ajbarea/techne
/plugin install techne@techne
Skills become available as techne:<name> and can be invoked the same way as any other Claude Code skill.
First-time setup: techne is opinionated about a few conventions (Makefile pattern, dev-runner archive,
.claude/skill-context.md). See Conventions for the minimum each skill needs.
Configuration
techne:sisters reads ~/.claude/techne.toml at runtime (user-controlled config that lists the active sister repos to compare against).
github_user = "your-github-username"
workspace_root = "/path/to/your/workspace"
[[sisters]]
name = "repo-one"
status = "active"
[[sisters]]
name = "repo-two"
status = "active"
[[sisters]]
name = "repo-three"
status = "active"
Set status = "backburner" to skip a repo without removing it.
How it fits together
~/.claude/techne.toml ← user-controlled sister-repo registry
│
▼
techne (plugin)
├── audit ── verifies build targets vs. logs/
├── auto-commit ── groups diffs into COMMITS.md
├── ci-audit ── reads gh runs, fixes warnings in-repo
├── deslop ── flags AI-slop prose
├── docs-site ── manages Zensical site + deploy
├── docsync ── doc claims ↔ implementation
├── reslop ── rewrites docstrings from code
├── sisters ── cross-repo drift across sisters
└── theoros ── observed tmux REPL session
Each skill is self-contained. Invoke one without pulling in the others. They share a convention of writing intermediate artifacts (plans, audit reports) to disk for human review before mutating the repo.
Why "techne"
Greek τέχνη: craft, the practical knowledge of how to make a thing well. That's what these skills are for — the craft of keeping a repo honest: audits, drift checks, clean commits, clean prose.
License
MIT.