Kiro integration: testers and contributors wanted (tracking issue)

オープン
#133 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
1週間以上
初心者へのやさしさ
32/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
nodejs, typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
0
フォーク
4
平均マージ
18時間 41分
マージ済み PR(30日)
48

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DiffCI/core のほかの issue

DiffCI/core の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。