Kiro integration: testers and contributors wanted (tracking issue)

Aberta
#133 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
32/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
nodejs, typescript

Direção de pesquisa

This is a tracking issue with four independent Kiro tasks, not a single change; pick one bullet before touching code. Start with docs/agent-installation.md#kiro to see the documented setup, then read what diffci init writes in packages/diffci-cli/src/client/agent-setup.ts and the stop hook in agent-stop.ts. The stop-hook item is research against Kiro's vendor docs first — done means either a cited doc showing a hook output that continues the agent, or a recorded finding that none exists. Other items are verified by running diffci init in a real Kiro session and reporting the observed payload.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement help wanted integration

DiffCI tells coding agents which tests and checks their change affects, so they verify before pushing. Since CLI 0.3.44, diffci init sets up Kiro: the MCP server in .kiro/settings/mcp.json (read-only tools auto-approved), the diffci-verify skill in .kiro/skills, and Kiro reads the AGENTS.md instructions init writes. Setup: docs/agent-installation.md#kiro. Kiro has no DiffCI stop hook yet, nothing has been tried in a real Kiro session, and this area is open for contributors.

Steps (each is one PR or one report; take any):

  • Kiro IDE and Kiro CLI: run diffci init and confirm the server, the auto-approved tools and the skill load.
  • Stop hook: Kiro has an Agent Stop trigger, but we found no documented output that makes the agent continue. Find out whether any documented hook output makes the agent continue (or another trigger does). If yes, add --agent kiro to diffci agent-stop; if no, record that here.
  • Custom agents: confirm the resources line in the docs loads the steering, AGENTS.md and the skill.
  • Windows: confirm the node -e launcher init writes starts the server.

Ground rules

  • When DiffCI cannot verify, the agent is told so and is never held: a failed setup must not look like a pass, and a pass must not be invented.
  • Verified behaviour only: link the vendor doc or show the payload you observed. If a vendor documents nothing, say so here rather than guessing.
  • Code lives in packages/diffci-cli/src/client/agent-setup.ts (what diffci init writes) and agent-stop.ts (the stop hook). Discuss design questions here, so every step stays consistent.

Area maintainer. Sustained work on this integration is how the Area maintainer tier is offered: named in the README and the docs, asked to review PRs that touch it, and co-author of the write-up when it ships.

Use Kiro and want to help, or have a repository we could test against? Say so below.

Linguagem predominante
TypeScript
Estrelas
0
Forks
4
Merge médio
18h 41min
PRs com merge (30d)
48

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de DiffCI/core

Todas as issues de DiffCI/core

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.