revise `argparse` of `main.py`

[kangwonlee]

• acfa103
• entrypoint.py seems more important?

[kangwonlee]

Opinion from Claude Sonnet 4

I'll help you understand the roles of main.py and entrypoint.py in your repository. Let me first examine these files to see their current implementation and purpose.Based on the code analysis, here's the role of each file:

main.py: Command-line interface for direct script execution

• Designed for manual/local use with command-line arguments
• Takes explicit parameters: --llm, --readme, --code, --json, etc.
• Outputs feedback to llm_comment.txt file
• Supports 3 LLM providers: Gemini, Grok, NVidia NIM

entrypoint.py: GitHub Actions entry point

• Designed for automated use in CI/CD workflows
• Reads configuration from environment variables (prefixed with INPUT_)
• Outputs to GitHub Step Summary and stdout
• Supports 5 LLM providers: Claude, Gemini, Grok, NVidia NIM, Perplexity
• Has more sophisticated API key handling and fallback logic

Should you remove one? No - they serve different purposes:

• Keep main.py for local development and testing
• Keep entrypoint.py for GitHub Actions integration

The dual structure is common in GitHub Actions that can also be used standalone. Both files share the same core logic but have different interfaces optimized for their respective use cases.

[kangwonlee]

Can main.py access all features ? Otherwise, should I revise the argparse interface ?

Based on my analysis, main.py cannot access all features available in entrypoint.py. Here are the key missing features:

Missing Features in main.py:

1. Multiple LLM providers:

   • main.py: Only 3 providers (Gemini, Grok, Nvidia NIM)
   • entrypoint.py: 5 providers (adds Claude, Perplexity)

2. Multiple input files:

   • main.py: Single file inputs (--code, --json)
   • entrypoint.py: Comma-separated multiple files via get_path_tuple()

3. Automatic LLM selection:

   • main.py: Must explicitly specify --llm
   • entrypoint.py: Smart fallback logic (single key → auto-select, multiple keys → prefer specified or fallback to Gemini)

4. Test failure validation:

   • main.py: Missing --fail-expected functionality
   • entrypoint.py: Has INPUT_FAIL-EXPECTED to assert expected test failures

5. GitHub integration:

   • main.py: Outputs to llm_comment.txt
   • entrypoint.py: Writes to GITHUB_STEP_SUMMARY, handles repository context

Recommendation: Yes, revise the argparse interface

Add these arguments to main.py:

parser.add_argument("--llm", choices=['claude', 'gemini', 'grok', 'nvidia_nim', 'perplexity'])
parser.add_argument("--code", help="Comma-separated student code files")
parser.add_argument("--json", help="Comma-separated pytest JSON reports")  
parser.add_argument("--fail-expected", action='store_true', help="Expect test failures")

This would make main.py feature-complete for local development while maintaining the specialized GitHub Actions interface in entrypoint.py.