issue-tracking

SKILL.md

Issues describe what needs to be done and why. Keep them high-level unless the user provides specific details.

When possible, include verification steps or hints that tell the implementing agent how to prove the issue is resolved. This helps ensure work is actually verified before being marked complete.

Why include verification? Agents should never claim work is done without evidence. If the issue itself describes how to verify, the implementing agent can follow those steps and provide concrete proof (command output, test results, screenshots, etc.).

プロジェクトの問題追跡システム。問題を作成、読み取り、更新、一覧表示、または閉じるときに使用します。 「問題の作成」、「バグの追加」、「タスクの追跡」、「問題のリスト」、「バグの表示」、「未解決のもの」、「問題のクローズ」、または任意の問題/バグ/タスク管理リクエストをトリガーします。 ソース: miketromba/issy。

原文を見る