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

generator-fix-integrator

Desenvolvimento Autor: redker56

Internal Auto-Harness generator skill for worktree-merge fix integration. Use only inside the parallel Generator integrator when it is addressing named defects from QA or retest.

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-fix-integrator/svg)](https://www.skillteca.com.br/skills/generator-fix-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 Fix Integrator

This skill governs Generator fix 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 when the named defects touch UX, layout, or interaction rules.
  • .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
  • .harness-parallel/qa/sprint-XX-qa-report.md
  • .harness-parallel/qa/sprint-XX-retest.md when the current fix cycle follows a failed retest.
  • .harness-parallel/qa/sprint-XX-fix-log.md when revising the current sprint fix log.

Then inspect the current project implementation relevant to this action:

  • Read the source files, routes, components, services, tests, and config touched by the named defects and the necessary regression surface around them.
  • 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/fix-log.md
  • references/templates/runtime-template.md

Follow these rules:

  • Merge only the worker branches the Orchestrator names for the current pass.
  • If not all temporary fix nodes are merged yet, perform merge work only and return structured merge results without writing .harness-parallel/qa/sprint-XX-fix-log.md or updating runtime notes.
  • Once all fix-workstream nodes are merged, finish any tightly related cleanup still required for the named defects.
  • Fix only defects named in the current QA or retest context unless a tightly related adjustment is required.
  • Treat the current sprint review, when present, as implementation guidance and cautions that still apply during the fix cycle.
  • Treat the Orchestrator's named bug batches plus ## Parallel Execution State as the source of truth for merge ordering.
  • Update the runtime contract when startup, access, or healthcheck behavior changed.
  • Record the actual fixes in the sprint fix log.
  • Keep the fix log tied to named defects, changed files, and any verification notes that matter for retest.
  • Do not rewrite QA or retest artifacts yourself.
Compartilhar X LinkedIn