S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

generator-build-integrator

Desenvolvimento Autor: redker56

Internal Auto-Harness generator skill for worktree-merge build integration. Use only inside the parallel Generator integrator during build mode.

13estrelas
Atualizado há 6 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add redker56/auto-harness

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/generator-build-integrator/svg)](https://www.skillteca.com.br/skills/generator-build-integrator)
#test

Skills relacionadas

Ver todas de Desenvolvimento →

claude-api

153.1k

Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a C

Desenvolvimento #ai #api por anthropics

skill-creator

153.1k

Crie novas skills, modifique e aprimore as existentes, e meça seu desempenho. Utilize para desenvolver, editar, otimizar, testar e comparar skills, além de refinar suas descrições para maior precisão de acionamento.

Desenvolvimento #test por anthropics

claude-code-plugin-release

83.4k

Fluxo de trabalho automatizado de versionamento semântico e lançamento para plugins do Claude Code. Gerencia incrementos de versão em manifestos package.json, marketplace.json, plugin.json, publicação npm (para que npx claude-mem@X.Y.Z seja resolvido), verificação de build, marcação git, lançamentos no GitHub e geração de changelog.

Desenvolvimento #ai #git por thedotmack

claude-mem

83.4k

Contexto Persistente Entre Sessões para Cada Agente – Captura tudo o que seu agente faz durante as sessões, comprime com IA e injeta contexto relevante de volta em sessões futuras. Compatível com Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode e mais.

Desenvolvimento #ai por thedotmack

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Generator Build Integrator

This skill governs Generator build integration mode.

At the start of this action, read these harness artifacts from the project:

  • .harness-parallel/status.md
  • .harness-parallel/intake.md
  • .harness-parallel/spec.md
  • .harness-parallel/design-direction.md
  • .harness-parallel/contracts/sprint-XX-contract.md
  • .harness-parallel/contracts/sprint-XX-review.md when it exists for the current sprint.
  • .harness-parallel/runtime.md when revising an existing runtime contract.
  • .harness-parallel/qa/sprint-XX-self-check.md when revising an existing self-check.

Then inspect the current project implementation relevant to this action:

  • Read the source files, routes, components, services, tests, and config needed to integrate the approved sprint scope.
  • Treat the main worktree as the integration surface and the worker branches named by the Orchestrator as merge inputs.

Then read these skill references:

  • references/protocols/file-ownership.md
  • references/templates/runtime-template.md
  • references/templates/self-check.md

Follow these rules:

  • Merge only the worker branches the Orchestrator names for the current pass.
  • If not all graph nodes are merged yet, perform merge work only and return structured merge results without writing .harness-parallel/runtime.md or the sprint self-check.
  • Once all graph nodes are merged, finish any tightly related seam cleanup needed to satisfy the approved sprint scope.
  • Treat the current sprint review, when present, as implementation guidance even if the verdict is already APPROVED.
  • Treat the contract dependency graph as the source of truth for ownership and merge ordering.
  • Update .harness-parallel/runtime.md so Evaluator can start and verify the app.
  • Make runtime.md sufficient for Evaluator to install, start, and health-check the app without follow-up questions.
  • Produce the current sprint self-check before handoff.
  • Do not quietly violate locked architecture or stack choices; surface unavoidable deviations explicitly in runtime notes and the self-check.
  • Do not modify orchestrator- or evaluator-owned artifacts.
Compartilhar X LinkedIn