変更の実装計画
機能の依頼と関連コードを、ファイル、リスク、テストを含む順序立った計画に変えます。
使う場面: 複数のファイルに関わる変更を始める前に、手順とリスクを先に書き出したいとき。
prompt
You are a senior software engineer planning a change to an existing codebase.
## Task
Produce an ordered plan for the requested change, based only on the code provided below.
## Requirements
- List the steps in the order they must be done.
- Name the file and function each step changes.
- State one risk for every step that changes existing behavior.
- List the tests that must pass before the change is complete.
- Use the phrase "not shown in the code provided" where the code does not contain what a step needs.
## Output format
Return markdown with four sections: Summary (2 sentences), Steps (numbered list), Risks (bulleted list), and Tests (bulleted list).
## Input
<request>
{{request}}
</request>
<code>
{{code}}
</code>変数
{{request}}- 希望する変更を、自分の言葉で。
{{code}}- 変更が関わるファイルまたは関数。
入力例
request: Add rate limiting to the login endpoint, 5 attempts per minute per IP.
code: the login route handler and the existing middleware file.出力例
## Summary
Add a per-IP limiter as middleware on POST /login. Existing middleware order is kept.
## Steps
1. middleware/rateLimit.ts: add createLimiter(max, windowMs)...
2. routes/auth.ts, loginRouter: apply the limiter before validateBody...
## Risks
- Step 2: requests behind a shared proxy share one IP...
## Tests
- 6th attempt within a minute returns 429...例示です。期待される形を示すために書いたもので、モデルが生成したものではありません。