Amazon Q Developer Prompts

Use the Amazon Q Developer /dev agent in [IDE_NAME] to implement this feature: '[FEATURE_DESCRIPTION]'. Point it at the [MODULE_NAME] module, let it propose a multi-file plan first, and review the plan for [CONCERN, e.g. database migration safety] before approving. Ask Q to write the implementation, add unit tests covering [TEST_SCENARIOS], and update [DOC_FILE]. Approve or reject each diff it proposes; do not let it commit anything directly to [BRANCH_NAME].

Run an Amazon Q Developer code transformation job to upgrade my Java [OLD_VERSION] codebase in [PROJECT_PATH] toward Java [NEW_VERSION]. Scope it to the [MODULE_NAME] module first ([LOC] lines of code, inside the free [FREE_LOC]/mo or Pro [PRO_LOC]/mo pooled quota). Ask Q to fix deprecated APIs, update dependency versions in [BUILD_FILE], and flag any code that needs manual review. Run the full test suite after transformation and report every behavioral change it made.

Use Amazon Q Developer to port my .NET Framework [OLD_VERSION] application [APP_NAME] to cross-platform .NET [NEW_VERSION]. Have Q scan the solution for Windows-only APIs, generate a porting report listing [REPORT_ITEMS], and produce the transformed projects with updated [CSPROJ] files. Ask it to flag third-party libraries without .NET [NEW_VERSION] equivalents so I can find replacements for [LIBRARY_1] and [LIBRARY_2] before the build breaks.

Ask Amazon Q Developer to generate [IAC_TOOL, e.g. CDK in TypeScript] for this architecture: '[ARCHITECTURE_DESCRIPTION]' in the AWS region [REGION]. The stack must include [SERVICE_1], [SERVICE_2], and [SERVICE_3], with least-privilege IAM roles and cost tags [TAG_KEY]=[TAG_VALUE]. Have Q explain each resource it creates, then validate the template with [VALIDATION_TOOL] before deploying to the [ENVIRONMENT] account.

Run Amazon Q Developer security scanning on the [REPO_NAME] repository and triage the findings. For each exposed credential or log injection issue it flags in [FILE_PATTERN], ask Q to propose a fix: move secrets to [SECRET_MANAGER], sanitize log inputs in [FUNCTION_NAME], and add a regression test. Prioritize findings in [CRITICAL_PATH] first. Document every remediation in [SECURITY_LOG] for the [COMPLIANCE_FRAMEWORK] audit.

Use the Amazon Q Developer CLI agent with MCP server support to perform this ops task: '[TASK_DESCRIPTION]' on the AWS account [ACCOUNT_ALIAS]. Grant it permission to run shell commands and call AWS APIs, but require approval before any command that modifies [PROTECTED_RESOURCE]. Have it read the current state of [SERVICE], propose the change as a plan, execute it, and print a verification summary with [METRICS] afterward.

Open the Amazon Q Developer chat in [IDE_NAME] and debug this production issue: '[ERROR_MESSAGE]' occurring in [SERVICE_NAME] since [TIMESTAMP]. Give Q context by opening [FILE_1] and [FILE_2], and ask it to trace the data flow from [ENTRY_POINT] to the failing line. Have it suggest [NUMBER] hypotheses ranked by likelihood, then a minimal reproduction in [TEST_FRAMEWORK]. Apply the fix it recommends only after the reproduction confirms the root cause.

Use Amazon Q Developer to convert the embedded Oracle SQL in [MODULE_NAME] to PostgreSQL for the [DATABASE_NAME] migration. Have it rewrite [STORED_PROCEDURE_1] and [STORED_PROCEDURE_2], replacing Oracle-specific [FEATURE, e.g. CONNECT BY] with Postgres equivalents, and flag any logic that has no direct translation. Ask Q to generate data validation queries comparing row counts between the Oracle and Postgres instances before cutover.

Ask Amazon Q Developer to analyze my AWS bill for account [ACCOUNT_ALIAS] over the last [MONTHS] months. Have it identify the top [NUMBER] cost drivers across [SERVICE_1] and [SERVICE_2], flag idle resources in [REGION], and estimate savings from [RIGHTSIZING_ACTION]. Ask for a prioritized action list with estimated monthly savings per item, and have it draft the CLI commands to implement the first [NUMBER] actions.

Have the Amazon Q Developer agent generate unit tests for [CLASS_OR_FUNCTION] in [LANGUAGE] using [TEST_FRAMEWORK]. The tests must cover [SCENARIO_1], [SCENARIO_2], and the edge case [EDGE_CASE]. Ask Q to follow the existing test style in [EXAMPLE_TEST_FILE] and to mock [DEPENDENCY_1] and [DEPENDENCY_2]. Run the suite and require [COVERAGE]% coverage on the new code before merging to [BRANCH].