Issue2Dev v0.1.0

Repository-aware implementation planning for GitHub Issues using deterministic Repository Intelligence.

This is the initial public release of Issue2Dev. The surface is intentionally small and offline-first: one command, deterministic output, and no AI provider calls.

Highlights

• Repository Intelligence Engine — builds a bounded RepositoryContext before any artifact is generated. Generation always consumes repository context, never raw issue text alone.
• Deterministic engineering diagnosis — produces root cause hypotheses, a recommended solution strategy, an implementation plan, and a test strategy, each with confidence scores, evidence, and explicit limitations. Diagnosis is deterministic and heuristic-based; no code is executed and no AI provider is used.
• Deterministic, no-provider output — the same input produces identical output. No AI/LLM calls; nothing to configure.
• Evidence & provenance — every heuristic carries a confidence score and source evidence; artifacts include a content hash and explicit caveats.
• Read-only GitHub ingestion — reads an issue and repository signals; writes only local files.

The CLI

A single command, issue2dev analyze:

# Analyze a local issue file (fully offline)
issue2dev analyze --from-file examples/from-file/issue-42.json --out .issue2dev/42

# Analyze a GitHub issue (read-only)
issue2dev analyze --repo owner/repo --issue 123 --out .issue2dev/123

Each run writes five files under .issue2dev/:

File	Purpose
repository-context.json	The deterministic RepositoryContext consumed by analysis and generation.
analysis.json	Structured analysis with scores, classification, and diagnosis (root cause hypotheses, solution strategy, implementation plan, test strategy, risks).
analysis.md	Human-readable engineering diagnosis: root cause hypotheses, solution strategy, implementation plan, test strategy, confidence, and limitations.
artifacts.json	Structured artifact bundle (machine-readable).
prd.md	Deterministic, repository-grounded PRD with problem statement, recommended solution, acceptance criteria, test strategy, risks, and open questions.

Requirements

• Node.js >= 20
• pnpm 10 (Corepack resolves the correct version automatically)

Install from source

git clone https://github.com/sinhoneyy/issue2dev.git
cd issue2dev
pnpm install
pnpm run build
pnpm exec issue2dev analyze --from-file examples/from-file/issue-42.json --out .issue2dev/42

Notes

• Issue2Dev is read-only toward GitHub and treats issue text as untrusted input.
• Diagnosis is deterministic and heuristic-based: it does not execute code, call AI providers, or claim exact fixes. All hypotheses are confidence-scored and grounded in repository evidence.
• See the README Limitations and Roadmap sections for exactly what is — and is not — implemented in v0.1.

Full documentation: README · Getting Started · CLI Reference