id stringlengths 9 9 | dataset_name stringclasses 1
value | version stringclasses 1
value | task_type stringclasses 4
values | language stringclasses 1
value | domain stringclasses 8
values | difficulty stringclasses 3
values | request stringclasses 175
values | context dict | analysis stringclasses 117
values | plan listlengths 5 5 | expected_output dict | target_behavior listlengths 5 5 | tags listlengths 4 4 | metadata dict | reference_signal dict | repo_tree dict | README_excerpt stringclasses 3
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
jlv1_0201 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Design a clean way to support CSV export in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"keep response latency low... | This is a feature-planning request for CSV export in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0202 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Introduce multi-file upload with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"keep response latency low",
"support Python 3.10+",
"limit changes to 2-3 files when possible"
],
"no... | This is a feature-planning request for multi-file upload in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0203 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Introduce caching with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"keep backwa... | This is a feature-planning request for caching in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call out... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0204 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Introduce rate limiting with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"preserve current public API",
"prefer explicit types and docstrings",
"keep backward compa... | This is a feature-planning request for rate limiting in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0205 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Introduce multi-file upload with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"avoid adding new dependencies",
"keep response late... | This is a feature-planning request for multi-file upload in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0206 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Introduce caching with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"preserve current public API",
"ensure tests are easy to run locally",
"limit changes to 2-... | This is a feature-planning request for caching in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0207 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Introduce webhook delivery with minimal changes and clear validation steps. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep backward compatibility",
"preserve current public API",
"limit changes to 2-3 files ... | This is a feature-planning request for webhook delivery in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0208 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Design a clean way to support audit logging in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"support Python 3.10+",
"avoid adding new dependencies",
"limit changes to 2-3 files w... | This is a feature-planning request for audit logging in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0209 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Add webhook delivery to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"ensure tests are easy to run locally",
"limit changes to 2-3 files when possi... | This is a feature-planning request for webhook delivery in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0210 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Design a clean way to support JWT login in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"preserve current public API",
"limit changes to 2-3 files when possible",
"ensure tests ar... | This is a feature-planning request for JWT login in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0211 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Extend the codebase to support CSV export while keeping the API stable. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"ensure tests are easy to run locally",
"prefer explicit types and docstrings",
"li... | This is a feature-planning request for CSV export in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0212 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Extend the codebase to support timezone-aware scheduling while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"support Python 3.10+",
"keep response latency low",
"avoid adding new dependencies"
],
... | This is a feature-planning request for timezone-aware scheduling in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important ed... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0213 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Extend the codebase to support multi-file upload while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"prefer explicit types and docstrings",
"limit changes to 2-3 files when possible",
... | This is a feature-planning request for multi-file upload in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0214 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Design a clean way to support JWT login in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"preserve current public API",
"limit changes to 2-3 files when possible",
"prefer explicit types... | This is a feature-planning request for JWT login in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0215 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Add multi-file upload to the testing utility package without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"keep backward comp... | This is a feature-planning request for multi-file upload in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0216 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Design a clean way to support webhook delivery in the current Python project. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep backward compatibility",
"... | This is a feature-planning request for webhook delivery in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0217 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Add search filters to the FastAPI service without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep response latency low",
"p... | This is a feature-planning request for search filters in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0218 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Design a clean way to support multi-file upload in the current Python project. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"keep backward compatibility",
"preserve current public API",
"prefer explicit types and do... | This is a feature-planning request for multi-file upload in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0219 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Introduce CSV export with minimal changes and clear validation steps. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"prefer explicit types and docstrings",
"ensure tests are easy to run locally",
"a... | This is a feature-planning request for CSV export in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0220 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Add pagination to the FastAPI service without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"keep response latency low",
"avoid adding new dependencies",
"limit changes... | This is a feature-planning request for pagination in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0221 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Introduce pagination with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"support Python 3.10+",
"preserve current public API",
"keep backward compatibility"
],
"note... | This is a feature-planning request for pagination in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0222 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Extend the codebase to support caching while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"avoid adding new dependencies",
"keep backward compatibility",
"support Python 3.10+"
],... | This is a feature-planning request for caching in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0223 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Design a clean way to support caching in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"preserve current public API",
"prefer explicit types and docstrings",
"support Py... | This is a feature-planning request for caching in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call out... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0224 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Extend the codebase to support async task retries while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"preserve current public API",
"ensure tests are easy to run locally",
"limit changes ... | This is a feature-planning request for async task retries in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of async task retries in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases."... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0225 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Add pagination to the background worker without breaking existing behavior. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrings",
"s... | This is a feature-planning request for pagination in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Cal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0226 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Introduce multi-file upload with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep backward compatibility",
"preserve current public API",
"prefer explicit types and docstrings"
],
... | This is a feature-planning request for multi-file upload in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0227 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Introduce background cleanup jobs with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"preserve current public API",
"keep backward compatibility",
"prefer expli... | This is a feature-planning request for background cleanup jobs in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edg... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0228 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Extend the codebase to support caching while keeping the API stable. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"prefer explicit types and docstrings",
"ensure tests are easy to run locally",
"avoid ad... | This is a feature-planning request for caching in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0229 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Introduce CSV export with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"support Python 3.10+",
"keep backward compatibility",
"avoid adding new dependencies"
]... | This is a feature-planning request for CSV export in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0230 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Extend the codebase to support webhook delivery while keeping the API stable. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"prefer explicit types and docstrings",
"preserve current public API",
"kee... | This is a feature-planning request for webhook delivery in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0231 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Introduce CSV export with minimal changes and clear validation steps. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"keep response latency low",
"keep backward compatibility",
"preserve cu... | This is a feature-planning request for CSV export in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Cal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0232 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Introduce search filters with minimal changes and clear validation steps. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"preserve current public API",
"support Python 3.10+",
"ensure tests are eas... | This is a feature-planning request for search filters in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0233 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Extend the codebase to support pagination while keeping the API stable. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"avoid adding new dependencies",
"support Python 3.10+",
"keep response lat... | This is a feature-planning request for pagination in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0234 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Add multi-file upload to the web scraping toolkit without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"ensure tests are easy to ru... | This is a feature-planning request for multi-file upload in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0235 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Extend the codebase to support background cleanup jobs while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"preserve current public API",
"ensure tests are easy to run locally",
"support Python 3.10+"
],
... | This is a feature-planning request for background cleanup jobs in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important e... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0236 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Introduce timezone-aware scheduling with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"ensure... | This is a feature-planning request for timezone-aware scheduling in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0237 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Design a clean way to support multi-file upload in the current Python project. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep backward compatibility",
"avoid adding new dependencies",
"keep response late... | This is a feature-planning request for multi-file upload in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0238 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Design a clean way to support pagination in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"preserve current public API",
"support Python 3.1... | This is a feature-planning request for pagination in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0239 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Extend the codebase to support caching while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"preserve current public API",
"support Python 3.10+"
... | This is a feature-planning request for caching in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0240 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Introduce webhook delivery with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"ensure tests are easy to run l... | This is a feature-planning request for webhook delivery in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases."... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0241 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Design a clean way to support CSV export in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep response latency low",
"suppo... | This is a feature-planning request for CSV export in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0242 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | easy | Extend the codebase to support rate limiting while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"support Python 3.10+",
"keep response latency low",
"preserve curre... | This is a feature-planning request for rate limiting in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0243 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Add JWT login to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"avoid adding new dependencies"... | This is a feature-planning request for JWT login in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0244 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Introduce caching with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"keep response latency low",
"limit changes to 2-3 files when p... | This is a feature-planning request for caching in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call o... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0245 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Design a clean way to support timezone-aware scheduling in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep response latency low",
"avoid adding new dependenc... | This is a feature-planning request for timezone-aware scheduling in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edg... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0246 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Extend the codebase to support async task retries while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"keep backward compatibility",
"preserve current public API",
"keep response latency low"
... | This is a feature-planning request for async task retries in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of async task retries in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0247 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Design a clean way to support webhook delivery in the current Python project. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"avoid adding new dependencies",
"keep backward compatibility",
"preserve cu... | This is a feature-planning request for webhook delivery in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0248 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | easy | Extend the codebase to support webhook delivery while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrings",
"keep ... | This is a feature-planning request for webhook delivery in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0249 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Add caching to the background worker without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"ensure tests ar... | This is a feature-planning request for caching in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call o... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0250 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Design a clean way to support webhook delivery in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"preserve current public API",
"support Python 3.10+",
"keep response latency low"
],
"notes... | This is a feature-planning request for webhook delivery in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases."... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0251 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | medium | Analyze the failure pattern caused by incorrect exception handling and propose a fix path. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"preserve current public API",
"prefer explicit types and docstrings",
"ensure tests are ... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0252 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | Flask admin dashboard | hard | Analyze the failure pattern caused by incorrect exception handling and propose a fix path. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"keep response latency low",
"avoid adding new dependencies",
"ensure tests are easy to run... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0253 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | medium | Analyze the failure pattern caused by unsafe string interpolation and propose a fix path. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"preserve current public API",
"ensure tests are easy to run locally",
"keep response late... | The signal suggests a bug linked to unsafe string interpolation. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the unsafe string interpolation.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "unsafe string interpolation"
} | null | null |
jlv1_0254 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | FastAPI service | medium | Find the root cause of a likely missing return value in this Python service. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"keep response latency low",
"ensure tests are easy to run locally",
"avoid ... | The signal suggests a bug linked to missing return value. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the missing return value.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "missing return value"
} | null | null |
jlv1_0255 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | medium | Debug a case where the app shows a invalid JSON parsing during normal usage. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep response latency low",
"support Python 3.10+",
"avoid adding new depen... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0256 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | Flask admin dashboard | easy | Analyze the failure pattern caused by off-by-one error and propose a fix path. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"li... | The signal suggests a bug linked to off-by-one error. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the off-by-one error.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal rep... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "off-by-one error"
} | null | null |
jlv1_0257 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | hard | Debug a case where the app shows a broken pagination cursor during normal usage. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"support Python 3.10+",
"avoid adding new dependencies"
],
"no... | The signal suggests a bug linked to broken pagination cursor. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the broken pagination cursor.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a min... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "broken pagination cursor"
} | null | null |
jlv1_0258 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | background worker | easy | Explain why the current implementation produces a state leak between requests and how to repair it. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"support Python... | The signal suggests a bug linked to state leak between requests. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the state leak between requests.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "state leak between requests"
} | null | null |
jlv1_0259 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | FastAPI service | hard | Explain why the current implementation produces a incorrect exception handling and how to repair it. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"avoid adding new dependencies",
"prefer explici... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0260 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | data processing library | easy | Explain why the current implementation produces a wrong default argument and how to repair it. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"preserve current ... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "wrong default argument"
} | null | null |
jlv1_0261 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | authentication module | easy | Explain why the current implementation produces a invalid JSON parsing and how to repair it. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"support Python 3.10+",
"avoid adding new dependencies",
"keep response latency low"
],
"notes": [
... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0262 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | medium | Explain why the current implementation produces a race condition in worker and how to repair it. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"keep response latency low",
"prefer explicit types and docstrings",
"keep backwar... | The signal suggests a bug linked to race condition in worker. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the race condition in worker.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a min... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "race condition in worker"
} | null | null |
jlv1_0263 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | hard | Explain why the current implementation produces a broken pagination cursor and how to repair it. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep backward compatibility",
"support Py... | The signal suggests a bug linked to broken pagination cursor. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the broken pagination cursor.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a min... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "broken pagination cursor"
} | null | null |
jlv1_0264 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | background worker | hard | Debug a case where the app shows a invalid JSON parsing during normal usage. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"support Python 3.10+",
"keep response ... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0265 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | Flask admin dashboard | medium | Find the root cause of a likely wrong default argument in this Python service. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "wrong default argument"
} | null | null |
jlv1_0266 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | data processing library | hard | Explain why the current implementation produces a unsafe string interpolation and how to repair it. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"keep backward compatibility",
"prefer explicit types and docstrings",
"limit changes to ... | The signal suggests a bug linked to unsafe string interpolation. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the unsafe string interpolation.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "unsafe string interpolation"
} | null | null |
jlv1_0267 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | medium | Explain why the current implementation produces a invalid JSON parsing and how to repair it. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"preserve current public API",
"keep response latency low",
"limit changes to 2-3 f... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0268 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | medium | Debug a case where the app shows a duplicate database writes during normal usage. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep response latency low",
"limit changes to 2-3... | The signal suggests a bug linked to duplicate database writes. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the duplicate database writes.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a mi... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "duplicate database writes"
} | null | null |
jlv1_0269 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | hard | Debug a case where the app shows a off-by-one error during normal usage. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"ensure tests are easy to run locally",
"prefer explicit types and docstrings",
... | The signal suggests a bug linked to off-by-one error. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the off-by-one error.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal rep... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "off-by-one error"
} | null | null |
jlv1_0270 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | FastAPI service | easy | Explain why the current implementation produces a unsafe string interpolation and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"keep response latency low",
"ensure tests are easy to run locally",
"prefer... | The signal suggests a bug linked to unsafe string interpolation. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the unsafe string interpolation.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "unsafe string interpolation"
} | null | null |
jlv1_0271 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | easy | Explain why the current implementation produces a wrong default argument and how to repair it. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"preserve current public API",
"limit changes to 2-3 files when possible",
"ensure ... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "wrong default argument"
} | null | null |
jlv1_0272 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | data processing library | hard | Explain why the current implementation produces a off-by-one error and how to repair it. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"ensure tests are easy to run locally",
"support Python 3.10+",
"avoid adding new ... | The signal suggests a bug linked to off-by-one error. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the off-by-one error.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal rep... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "off-by-one error"
} | null | null |
jlv1_0273 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | authentication module | easy | Explain why the current implementation produces a invalid JSON parsing and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep backward compatibility",
"ensure tests are easy to run locally",
"avoid adding new de... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0274 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | medium | Explain why the current implementation produces a invalid JSON parsing and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"ensure tests are easy to run locally",
"avoid adding new dependencies",
"support Py... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0275 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | medium | Explain why the current implementation produces a unsafe string interpolation and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"support Python 3.10+",
"avoid adding new dependencies",
"preserve current p... | The signal suggests a bug linked to unsafe string interpolation. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the unsafe string interpolation.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "unsafe string interpolation"
} | null | null |
jlv1_0276 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | hard | Analyze the failure pattern caused by incorrect exception handling and propose a fix path. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"prefer explicit types and docstrings",
"preserve current public API",
"support Python 3.10+... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0277 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | medium | Explain why the current implementation produces a missing return value and how to repair it. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrin... | The signal suggests a bug linked to missing return value. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the missing return value.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "missing return value"
} | null | null |
jlv1_0278 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | easy | Debug a case where the app shows a missing return value during normal usage. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"prefer explicit types and docstrings",
"ensure tests are easy to run lo... | The signal suggests a bug linked to missing return value. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the missing return value.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "missing return value"
} | null | null |
jlv1_0279 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | easy | Debug a case where the app shows a invalid JSON parsing during normal usage. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"preserve current public API",
"keep backward compatibility",
"keep response... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0280 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | FastAPI service | medium | Analyze the failure pattern caused by invalid JSON parsing and propose a fix path. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"support Python 3.10+",
"keep backward compatibility",
"limit change... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0281 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | Flask admin dashboard | medium | Find the root cause of a likely wrong default argument in this Python service. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"preserve current public API",
"support Python 3.10+",
"ensure test... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "wrong default argument"
} | null | null |
jlv1_0282 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | easy | Debug a case where the app shows a broken pagination cursor during normal usage. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"keep backward compatibility",
"limit changes to 2-3 files when possible",
"... | The signal suggests a bug linked to broken pagination cursor. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the broken pagination cursor.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a min... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "broken pagination cursor"
} | null | null |
jlv1_0283 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | easy | Analyze the failure pattern caused by duplicate database writes and propose a fix path. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"keep backward compatibility",
"limit changes to 2-3 files when possible",
"suppor... | The signal suggests a bug linked to duplicate database writes. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the duplicate database writes.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a mi... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "duplicate database writes"
} | null | null |
jlv1_0284 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | FastAPI service | hard | Debug a case where the app shows a off-by-one error during normal usage. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"lim... | The signal suggests a bug linked to off-by-one error. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the off-by-one error.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal rep... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "off-by-one error"
} | null | null |
jlv1_0285 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | easy | Explain why the current implementation produces a invalid JSON parsing and how to repair it. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"keep response latency low",
"avoid adding new dependencies",
"keep backward compatibility"
],
"notes"... | The signal suggests a bug linked to invalid JSON parsing. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the invalid JSON parsing.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "invalid JSON parsing"
} | null | null |
jlv1_0286 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | hard | Find the root cause of a likely wrong default argument in this Python service. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"ensure tests are easy to run locally",
"limit changes to 2-3 files when possibl... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "wrong default argument"
} | null | null |
jlv1_0287 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | medium | Explain why the current implementation produces a unsafe string interpolation and how to repair it. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep response latency low",
"preserve current publi... | The signal suggests a bug linked to unsafe string interpolation. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the unsafe string interpolation.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "unsafe string interpolation"
} | null | null |
jlv1_0288 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | medium | Explain why the current implementation produces a wrong default argument and how to repair it. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"avoid adding new dependencies",
"keep backward compatibility"
]... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "wrong default argument"
} | null | null |
jlv1_0289 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | easy | Debug a case where the app shows a incorrect exception handling during normal usage. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep response latency low",
"prefer explicit types and docstrings",
"ensure tests a... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0290 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | background worker | medium | Find the root cause of a likely state leak between requests in this Python service. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"support Python 3.10+",
"preserve current publ... | The signal suggests a bug linked to state leak between requests. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the state leak between requests.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "state leak between requests"
} | null | null |
jlv1_0291 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | Flask admin dashboard | easy | Debug a case where the app shows a incorrect exception handling during normal usage. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"support Python 3.10+",
"avoid adding new dependencies",
"limit cha... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0292 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | background worker | easy | Explain why the current implementation produces a duplicate database writes and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"support Python 3.10+",
"limit changes to 2-3 files when possible",
"avoid addin... | The signal suggests a bug linked to duplicate database writes. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the duplicate database writes.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a mi... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "duplicate database writes"
} | null | null |
jlv1_0293 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | background worker | easy | Find the root cause of a likely missing return value in this Python service. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"keep backward compatibility",
"limit changes to 2-3 files when possible",
"keep... | The signal suggests a bug linked to missing return value. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the missing return value.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A test started failing on edge-case input.",
"focus_area": "missing return value"
} | null | null |
jlv1_0294 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | CLI automation tool | medium | Explain why the current implementation produces a broken pagination cursor and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"prefer explicit ... | The signal suggests a bug linked to broken pagination cursor. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the broken pagination cursor.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a min... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "broken pagination cursor"
} | null | null |
jlv1_0295 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | hard | Explain why the current implementation produces a off-by-one error and how to repair it. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"preserve current public API",
"keep response latency low",
"support Python ... | The signal suggests a bug linked to off-by-one error. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the off-by-one error.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minimal rep... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "off-by-one error"
} | null | null |
jlv1_0296 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | hard | Find the root cause of a likely incorrect exception handling in this Python service. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"keep ba... | The signal suggests a bug linked to incorrect exception handling. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the incorrect exception handling.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "incorrect exception handling"
} | null | null |
jlv1_0297 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | FastAPI service | medium | Debug a case where the app shows a duplicate database writes during normal usage. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"avoid adding new dependencies",
"keep response latency low",
"keep backward compa... | The signal suggests a bug linked to duplicate database writes. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the duplicate database writes.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a mi... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "Unexpected behavior appears after a recent refactor.",
"focus_area": "duplicate database writes"
} | null | null |
jlv1_0298 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | web scraping toolkit | medium | Analyze the failure pattern caused by duplicate database writes and propose a fix path. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"preserve current public API",
"limit changes to 2-3 files when possible... | The signal suggests a bug linked to duplicate database writes. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the duplicate database writes.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a mi... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "The code passes locally but fails under repeated requests.",
"focus_area": "duplicate database writes"
} | null | null |
jlv1_0299 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | testing utility package | easy | Explain why the current implementation produces a duplicate database writes and how to repair it. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"limit chan... | The signal suggests a bug linked to duplicate database writes. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the duplicate database writes.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a mi... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "duplicate database writes"
} | null | null |
jlv1_0300 | JumpLander Agent Dataset | 1.0 | bug_analysis | python | Flask admin dashboard | easy | Explain why the current implementation produces a wrong default argument and how to repair it. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"preserve current public API",
"ensure tests are easy to run locally",
"avoid add... | The signal suggests a bug linked to wrong default argument. A strong response should explain the likely failure mode, isolate the affected layer, and recommend a fix that is small, testable, and compatible with the current contract. | [
"Identify the most likely root cause behind the wrong default argument.",
"Trace the data flow from input to failure point.",
"Check for incorrect assumptions, state mutation, or validation gaps.",
"Recommend a fix that preserves the original contract.",
"Describe how to verify the fix with tests or a minim... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"bug_analysis",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | {
"type": "issue_or_patch",
"summary": "A response payload changed format unexpectedly.",
"focus_area": "wrong default argument"
} | null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.