idd-skill: Instructions file for Gemini CLI

Guidelines for AI Agents

This repository distributes the IDD (Issue-Driven Development) workflow — a portable set of .github/instructions/ files that wire up a multi-agent issue-driven pipeline for any GitHub project.

Canonical reference: The full, authoritative project guidance lives in .github/copilot-instructions.md. This file contains tool-specific guidance for Antigravity CLI (formerly Gemini CLI). When Copilot-specific workflow names appear, apply the intent in Antigravity using Antigravity's own interaction model rather than following product terms literally.

Minimum requirements

• Match the conversational language to the user's language.
• Write comments and documentation in English unless there is a clear project-specific reason otherwise.
• When editing README.md, also apply the equivalent change to README.ja.md, and vice versa. Keep both files in sync in the same commit.
• Avoid hard-coded repository file counts in docs unless the number is mechanically maintained. If count-based wording is necessary, update every mirrored reference in the same commit.
• If uncertainty, hidden risk, or missing context blocks a safe change, stop and ask a concise question before proceeding.
• Keep changes small and reviewable. Follow the project's Conventional Commits rules and keep each commit atomic.
• Do not modify community documents (CODE_OF_CONDUCT*, CONTRIBUTING*) without explicit approval.

Project standards

• Indentation: 2 spaces
• Line endings: LF only
• Trailing whitespace: trimmed except in Markdown
• Final newline: always present
• File naming: lowercase with hyphens unless a platform convention requires otherwise
• Helper sources: the helper migration to TypeScript is complete — every scripts/*.mjs / bin/*.mjs is generated from a src/**/*.mts source by pnpm run build and committed; no hand-written helper .mjs path remains. .mts is the source of truth — edit the .mts, never the generated .mjs. See docs/typescript-sources.md.
• Inline code span wrapping: a code span may wrap at a word boundary but must never wrap mid-token (right after a hyphen, underscore, slash, or dot the token continues through) — CommonMark renders the break as a literal space and corrupts the token. Put a command too long for one line in a fenced code block instead. If the wrap-point character is a hand-added artifact rather than part of the real value, delete it instead of just relocating the break. Enforced by node scripts/audit-code-span-wrap.mjs (repository-local; not distributed to idd-template/).
• Bare issue/PR reference wrapping: a bare #NNN reference must never be the first token of a paragraph, list item, or wrapped continuation line in prose Markdown — dprint fmt's automatic line-wrap can relocate it there, and markdownlint's MD018 rule (no-missing-space-atx) then flags it as a malformed ATX heading. MD018 only fires at zero leading indentation, so it misses the same drift inside an indented list-item continuation line — do not rely on the linter alone. Prefer "issue #NNN" (or another phrasing that keeps a word before the #) whenever the reference could plausibly open a sentence, bullet, or wrapped line.