Turn GitHub issues into
repository-aware engineering plans.

Issue2Dev analyzes an issue with its repository context, then emits deterministic root-cause hypotheses, implementation plans, test strategy, and PRD artifacts locally, reviewably, and without GitHub writeback.

View on GitHub

Offline-friendly
Deterministic
Evidence-grounded
No code writeback
Read-only GitHub ingestion
No provider key required

GitHub issues rarely contain enough context to implement safely.

Raw issue text creates ambiguity. While generic AI improvises single-prompt guesses, Issue2Dev deterministically compiles AST context, traces citations, and builds inspectable planning artifacts.

Read-Only IngestionAST GroundingZero Writeback

issue2dev --issue 42

pipeline active

Ingesting issue payload·just now

local/issue-42.json (ID: 42)

Deterministic Compilation

Traces execution paths, flags risk hotspots, and compiles diagnosis in real time.

Inspect log engine

src/components/Navbar.tsx

TSX

›export function Navbar({ user })

98% AST MatchAST Verified

src/context/AuthContext.tsx

STATE

›const useAuth = () => useContext()

Session Hook TracedAST Verified

root/package.json

CONFIG

›"next": "^16.2", "tailwind": "v4"

Stack ResolvedAST Verified

src/app/api/route.ts

API

›export async function POST(req)

AST Hotspot FlaggedAST Verified

root/tsconfig.json

CONFIG

›"paths": { "@/*": ["./src/*"] }

Aliases MappedAST Verified

src/components/Navbar.tsx

TSX

›export function Navbar({ user })

98% AST MatchAST Verified

src/context/AuthContext.tsx

STATE

›const useAuth = () => useContext()

Session Hook TracedAST Verified

root/package.json

CONFIG

›"next": "^16.2", "tailwind": "v4"

Stack ResolvedAST Verified

src/app/api/route.ts

API

›export async function POST(req)

AST Hotspot FlaggedAST Verified

root/tsconfig.json

CONFIG

›"paths": { "@/*": ["./src/*"] }

Aliases MappedAST Verified

src/components/Navbar.tsx

TSX

›export function Navbar({ user })

98% AST MatchAST Verified

src/context/AuthContext.tsx

STATE

›const useAuth = () => useContext()

Session Hook TracedAST Verified

root/package.json

CONFIG

›"next": "^16.2", "tailwind": "v4"

Stack ResolvedAST Verified

src/app/api/route.ts

API

›export async function POST(req)

AST Hotspot FlaggedAST Verified

root/tsconfig.json

CONFIG

›"paths": { "@/*": ["./src/*"] }

Aliases MappedAST Verified

src/components/Navbar.tsx

TSX

›export function Navbar({ user })

98% AST MatchAST Verified

src/context/AuthContext.tsx

STATE

›const useAuth = () => useContext()

Session Hook TracedAST Verified

root/package.json

CONFIG

›"next": "^16.2", "tailwind": "v4"

Stack ResolvedAST Verified

src/app/api/route.ts

API

›export async function POST(req)

AST Hotspot FlaggedAST Verified

root/tsconfig.json

CONFIG

›"paths": { "@/*": ["./src/*"] }

Aliases MappedAST Verified

Repository Ingestion

Build context automatically from file imports, AST definitions, and local dependencies.

Explore scanner

Sandbox Active

0444 READ-ONLY

WRITEBACKDISABLED

GIT WORKTREEUNTOUCHED

Read-Only Sandbox

Zero code writeback. Pure read-only local analysis with untouched git working tree.

Security model

.issue2dev/42-cli/

Emitted

repository-context.jsonAST & topology graph

JSON4.2 KB

analysis.mdImpact & risk scoring

DIAG6.1 KB

prd.mdSafe implementation plan

SPEC3.9 KB

Offline Output Artifacts

Emits clean, structured markdown diagnostics and PRDs to .issue2dev/ output trees.

Explore artifacts

Grounding & Citations

Cites source file lines and AST locations for every single planning hypothesis generated.

Verify citations

How Issue2Dev processes issues

A pipeline structured for transparency. Every step exposes evidence paths.

Local File / API

Ingest Issue

Ingests raw issue input securely from local JSON configurations or directly via read-only GitHub API parameters.

Step 01 Ready

Intelligence Engine

Build RepositoryContext

Heuristically maps repository stacks, architecture signatures, risk zones, and component dependency graphs.

Step 02 Ready

Risk Scoring

Analyze

Calculates impact surface, assigns severity metrics, estimates risk profiles, and scores planning priorities.

Step 03 Ready

Root-Cause Solver

Diagnose

Emits localized root cause hypotheses, maps solution pathways, and drafts integration checkpoints.

Step 04 Ready

Outputs Produced

Generate Artifacts

Compiles reviewable markdown summaries and clean, schema-aligned JSON configuration trees under .issue2dev/

Step 05 Ready

Git-Diff Ready

Review

Allows developers to review complete project-scoped strategies side-by-side with original codebase branches.

Step 06 Ready

Why Issue2Dev?

Review issues like code, before writing code.

Context You Won’t Fake Anywhere

Issue2Dev builds repository context first — labeling uncertainty, preserving provenance, and producing reviewable planning artifacts engineers can inspect like code, not a single-prompt guess dressed up as an answer.

Full AST & Dependency Mapping

Maps cross-file imports, symbol definitions, and hierarchy chains.

Provenance-Preserved Planning

Every plan references exact source files and deterministic line boundaries.

Zero Code Writeback

Strictly read-only sandbox with zero destructive file alterations.

How does it compare?

Evaluating issue analysis strategies across context, accuracy, and infrastructure.

Capability	Raw Issue	Generic LLM Summary	Issue2Dev
Repository-Aware Context Detects file structures, languages, frameworks, and import dependencies.	Repository-Aware Context - Raw Issue: Not supported / No	Repository-Aware Context - Generic LLM Summary: Not supported / No	Repository-Aware Context - Issue2Dev: Supported / Yes
Deterministic & Reproducible Running it multiple times yields matching, evidence-linked results.	Deterministic & Reproducible - Raw Issue: Not supported / No	Deterministic & Reproducible - Generic LLM Summary: Not supported / No	Deterministic & Reproducible - Issue2Dev: Supported / Yes
Evidence & Provenance Tracking Attributes facts to specific lines of code or workspace configurations.	Evidence & Provenance Tracking - Raw Issue: Not supported / No	Evidence & Provenance Tracking - Generic LLM Summary: Not supported / No	Evidence & Provenance Tracking - Issue2Dev: Supported / Yes
Confidence-Labeled Heuristics Explicitly states prediction certainty scores (e.g. Affected Files).	Confidence-Labeled Heuristics - Raw Issue: Not supported / No	Confidence-Labeled Heuristics - Generic LLM Summary: Not supported / No	Confidence-Labeled Heuristics - Issue2Dev: Supported / Yes
Offline-Friendly (No Provider Call) Does not require internet access, external SaaS platforms, or remote keys.	Offline-Friendly (No Provider Call) - Raw Issue: Supported / Yes	Offline-Friendly (No Provider Call) - Generic LLM Summary: Not supported / No	Offline-Friendly (No Provider Call) - Issue2Dev: Supported / Yes
Treats Issue Text as Untrusted Filters claims, checks validation, and safeguards inputs before assembly.	Treats Issue Text as Untrusted - Raw Issue: Not supported / No	Treats Issue Text as Untrusted - Generic LLM Summary: Not supported / No	Treats Issue Text as Untrusted - Issue2Dev: Supported / Yes
No Vendor/API Key Required Can be executed locally without subscribing to API platforms or models.	No Vendor/API Key Required - Raw Issue: Supported / Yes	No Vendor/API Key Required - Generic LLM Summary: Not supported / No	No Vendor/API Key Required - Issue2Dev: Supported / Yes

Repository-Aware Context

Detects file structures, languages, frameworks, and import dependencies.

Raw Issue

Generic LLM Summary

Deterministic & Reproducible

Running it multiple times yields matching, evidence-linked results.

Raw Issue

Generic LLM Summary

Evidence & Provenance Tracking

Attributes facts to specific lines of code or workspace configurations.

Raw Issue

Generic LLM Summary

Confidence-Labeled Heuristics

Explicitly states prediction certainty scores (e.g. Affected Files).

Raw Issue

Generic LLM Summary

Offline-Friendly (No Provider Call)

Does not require internet access, external SaaS platforms, or remote keys.

Raw Issue

Generic LLM Summary

Treats Issue Text as Untrusted

Filters claims, checks validation, and safeguards inputs before assembly.

Raw Issue

Generic LLM Summary

No Vendor/API Key Required

Can be executed locally without subscribing to API platforms or models.

Raw Issue

Generic LLM Summary

Try the CLI locally

Install and run the Issue2Dev analyze compiler offline or connected to GitHub.

CLI Constraints

Output directories must live under a .issue2dev/ path (enforced).
The CLI currently exposes the analyze command.
GITHUB_TOKEN is optional for public issues, but recommended to avoid rate limits.

~/issue2dev

pnpm install

pnpm run build

Resolving workspace dependencies...

Compiling TypeScript source to dist/cli.js

✔Dependencies resolved (42 packages synchronized)

✔Built CLI distribution in 384ms -> dist/cli.js

✔Issue2Dev compiler ready for execution

Deterministic Local Output Bundles

Output planning artifacts

Issue2Dev compiles structured files containing diagnostics, plans, and requirements for direct peer review.

Reviewable engineering plans. Outputs are grouped in folders, allowing developers to inspect diagnostic details before writing any code.

repository-context.jsonEnvironment & Context

{

"context_version": "0.1.0",

"issue": {

"id": 42,

"title": "Bug: session drops on refresh"

"repository": {

"name": "issue2dev",

"languages": ["TypeScript"],

"frameworks": ["nextjs"]

"confidence_scores": {

"affected_files": 0.85,

"root_cause": 0.90

}

Ingested environment, repository dependencies, and confidence scores.

Designed to be inspectable,
bounded, and honest.

Issue2Dev is built for developers who audit their tools. We never write back to your repository, never modify your source files, and never make silent SaaS provider calls.

Read-Only Ingestion

All interactions with GitHub APIs are read-only. No write tokens are requested or utilized in execution.

Isolated Local Writes

Writes planning files exclusively under the local .issue2dev/ workspace folder. Code files remain unmodified.

Sanitized Entanglements

Treats issue text as untrusted. Normalizes variables and redacts environment properties automatically.

Inspectable Provenance

Every generated PRD is complete with grounding citations pointing back to source files and heuristics.

Verification Hash: SHA-256 Verified Offline Executable

Zero Server Storage: No Cloud Backends

Limitations of v0.1

We are upfront about what Issue2Dev can and cannot do. This is a technical utility, not a magic fix.

v0.1 is intentionally small

Only the single 'analyze' command exists. There are no additional interactive loops or multi-command features in this version.

No AI/LLM integration yet

All Repository Intelligence is 100% heuristic-driven, AST-based, and static rule-grounded. No generative neural nets are active.

Predictions are heuristics

Affected-file predictions are educated recommendations with confidence weights. They are not compile-time absolute guarantees.

GitHub API dependency

Remote GitHub issue retrieval requires active network connections and conforms to GitHub's standard hourly rate limits.

Primary Markdown Outputs:analysis.mdprd.md

Development roadmap

Planned future directions. These capabilities are not yet active in v0.1.

3 planned

Distribution

GitHub Action Integration
GitHub CLI (gh) extension wrapper
NPM-published global executable binary

4 planned

Intelligence

Semantic search & codebase embeddings
Deep import AST & dependency path resolver
Multi-language architecture pattern scans
Duplicate issue & regression detection

3 planned

Generation & Providers

Optional OpenAI / Anthropic provider hooks
Offline local models integration (Ollama / Llama.cpp)
Additional artifact schemas (issue templates)

4 planned

Interfaces

Model Context Protocol (MCP) server support
Visual Workspace Dashboard UI
VS Code & JetBrains extension modules
Pipeline plugins / lifecycle hooks API

Have feature requests or feedback? Open an issue

Review issues like code,
before writing code.

Start building repository context first. Build and review deterministic planning artifacts on your local terminal today.

Star on GitHub

Read README Contribute My Portfolio

Turn GitHub issues into repository-aware engineering plans.

GitHub issues rarely contain enough context to implement safely.

Deterministic Compilation

Repository Ingestion

Read-Only Sandbox

Offline Output Artifacts

Grounding & Citations

How Issue2Dev processes issues

Ingest Issue

Build RepositoryContext

Analyze

Diagnose

Generate Artifacts

Review

Why Issue2Dev?

Context You Won’t Fake Anywhere

Full AST & Dependency Mapping

Provenance-Preserved Planning

Zero Code Writeback

How does it compare?

Repository-Aware Context

Deterministic & Reproducible

Evidence & Provenance Tracking

Confidence-Labeled Heuristics

Offline-Friendly (No Provider Call)

Treats Issue Text as Untrusted

No Vendor/API Key Required

Try the CLI locally

Output planning artifacts

Designed to be inspectable, bounded, and honest.

Read-Only Ingestion

Isolated Local Writes

Sanitized Entanglements

Inspectable Provenance

Limitations of v0.1

v0.1 is intentionally small

No AI/LLM integration yet

Predictions are heuristics

GitHub API dependency

Development roadmap

Distribution

Intelligence

Generation & Providers

Interfaces

Review issues like code, before writing code.

Turn GitHub issues into
repository-aware engineering plans.

Designed to be inspectable,
bounded, and honest.

Review issues like code,
before writing code.