Kiro integration: testers and contributors wanted (tracking issue)

Offen
#133 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
32/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
nodejs, typescript

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
0
Forks
4
Ø Merge
18 Std. 41 Min.
Gemergte PRs (30 T.)
48

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus DiffCI/core

Alle Issues in DiffCI/core

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.