Developer Portfolio Repository Audit
Check pinned repositories as a hiring manager would.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Audit my developer portfolio. List of pinned repositories with README text and structure: [REPOSITORIES]. Languages and roles I want: [TARGET_ROLES]. Time a reviewer might spend: [REVIEW_TIME]. Review each repository for a clear purpose, setup instructions that work, tests, commit history, code organisation, security hygiene such as exposed secrets, and licence. Judge whether the set shows range or repetition and whether the best work is easy to find. Return a table with Repository, Strength, Weakness, Severity (red, amber, green) and Fix, an order for the pinned list, and a one-hour improvement plan. Tell me to rotate any secret that appears in history and to verify licence choices before publishing [VERIFY]. Include a quick scan of each repository for accidental personal data, private URLs, API keys in history and unmaintained dependencies with known problems. Suggest what a README should contain in six lines, and which repositories I should archive, since a smaller portfolio with working projects usually reads better.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.