prompt changes to code review action

[mdtux89]

No description provided.

[junie-github-actions]

Junie successfully finished!

Result: Review PR Diff and Update Documentation Accuracy

Documentation Review Complete

Reviewed the PR diff and verified all documentation is accurate and up-to-date.

Summary of Findings:

PR Changes Analysis:

• The PR only modifies src/constants/github.ts - specifically the internal code review instructions template
• Changes update Junie's internal workflow (replacing "answer tool" with "submit", clarifying commenting guidelines, refining review process)
• These are internal instructions for Junie's code review behavior, not user-facing features

Documentation Verification:

✅ action.yml inputs/outputs: All 22 inputs and 7 outputs are correctly documented in README.md

• Trigger Configuration: trigger_phrase, assignee_trigger, label_trigger ✓
• Branch Management: base_branch, create_new_branch_for_pr ✓
• Junie Configuration: prompt, junie_version, model, junie_work_dir, junie_guidelines_filename, allowed_mcp_servers ✓
• Advanced Features: resolve_conflicts, silent_mode, use_single_comment, attach_github_context_to_custom_prompt ✓
• Jira Integration: All 5 Jira inputs ✓
• Authentication: junie_api_key, custom_github_token ✓
• Outputs: All 7 outputs documented with examples ✓

✅ Code examples: All workflow examples in README.md are correct and match current implementation

✅ Features documentation: All features including inline code reviews are properly documented

✅ Configuration examples: Match actual implementation in action.yml

Conclusion:
No documentation updates needed. The PR changes are internal-only modifications that don't affect user-facing functionality or configuration.