/reference-check

The user wants to generate a grounded recommendation letter — every paragraph traced to real evidence — by running this repo's CLI (python -m reference_check). You are the interactive front door; the CLI does the real work (extract → narrate → ground → build letter → render). Do NOT write recommendation letter content yourself and do NOT edit any code.

Arguments (may be empty): $ARGUMENTS

Steps

1. Gather the inputs from $ARGUMENTS; ask the user for anything missing:

   • source type — one of github or web. If unclear, ask:
     • github → a GitHub repository, evidence is the author's merged PRs (via gh).
     • web → a blog/article URL, evidence is the fetched article.
   • source URL — https://github.com/<owner>/<repo> for github, or the article URL for web.
   • author — the GitHub handle of the developer being recommended (github), or the subject the letter is for (web).
   • optionally --out if the user wants the Markdown written to a file instead of shown inline.

2. Run the CLI with exactly those values (pass each as a separate argument — never assemble a shell string from the user's input, never use command substitution or quoted interpolation of $ARGUMENTS):

   python -m reference_check --source-type <type> --source <url> --author <author>
   

   Add --out <file> only if the user asked to save to a file. Use python (not python3) on this host.

3. On a non-zero exit, show the CLI's stderr message and help the user fix the input — e.g. an invalid/unsupported --source URL, or an unknown --source-type (the CLI validates and reports these). Do NOT retry with a guessed URL, author, or source type.

4. On success, show the user:

   • the rendered Markdown recommendation letter (or, with --out, confirm the file path), and
   • the grounding summary the CLI prints on stderr (grounded: N rejected: N needs-confirmation: N) so they can see how many claims were dropped for lacking real evidence.

Hard rules

• Use ONLY the source URL and author the user supplies. Never fabricate a repo, URL, PR, author, or file path to make the command produce output.
• This command's only job is to invoke python -m reference_check. Never bypass it, never hand-write recommendation letter content, and never modify reference_check/ or portfolio/ code to "make it work".
• Never assemble a shell string from user input. Pass each user-supplied value as a separate argv token to the CLI. No command substitution expansion, no shell string interpolation of $ARGUMENTS into a single command string.
• If the CLI reports a source type is unsupported, relay that — don't try to implement it here.
• The letter the CLI produces is grounded: every paragraph cites real evidence from the developer's actual work. Do not supplement or rewrite it.