docs(github): move PR template to GitHub idiomatic location (#9)

CHANGES
- Move PR template from PULL_REQUEST_TEMPLATE/ to root .github/
- Update commit message prompt with multi-issue linking format
- Update PR generation prompt with issue linking guidelines

IMPACT
- GitHub will automatically detect PR template in standard location
- Improved AI prompt consistency with KemingHe/common-devx standards

Author: KemingHe

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md renamed to .github/pull_request_template.md

@@ -36,6 +36,7 @@ Write final commit message and return in plaintext code block.
 type(scope): brief description in imperative mood
 
 closes #[issue-number] (if applicable)
+closes #[issue-number] (repeat for each resolved issue)
 
 CHANGES
 - Key change 1
@@ -55,7 +56,7 @@ TECHNICAL NOTES
 
 - **Title**: Max 50 characters, imperative mood ("add", "fix", "update")
 - **Content**: Only include sections with meaningful content, use dash bullets with no redundancy between items
-- **Issue linking**: Only include "closes #X" for actual issue resolution
+- **Issue linking**: Only include "closes #X" for actual issue resolution, use separate "closes" statements for each issue
 
 ## EXAMPLES
 

prompts/prompt-commit-msg-gen.md

@@ -36,6 +36,7 @@ You are a senior software engineer creating pull request descriptions that commu
 - **Analysis depth**: Analyze feature branch against main using git commands and GitHub MCP tools
 - **Content accuracy**: Preserve implementation details, performance impacts, architectural decisions
 - **Business context**: Connect technical changes to business value and user impact
+- **Issue linking**: Use separate "closes #[issue-number]" statements for each resolved issue to ensure proper GitHub recognition
 
 ## OUTPUT FORMAT