make-it-hireable
Make it hireable
The gap between a "college project" and "someone who can work on our codebase" is usually the same 8–10 things. This skill closes that gap in the candidate's real project, with them in the loop, so they can explain every change in an interview.
0. Setup
- Call the Skill tool with "cracked-profile" (target role shapes priorities: a backend role cares about APIs, tests and DB; frontend about performance, accessibility and UX).
- Confirm the project is the current directory and is a git repo. If it isn't a git repo, offer
git initplus an initial commit first, so every change is reversible. - Check
git status. If there are uncommitted changes, stop and ask them to commit or stash first.
1. Audit
Read the project: manifests, entry points, structure, config, tests, CI, deploy files, README. Score it against the checklist in CHECKLIST.md and show it as a table: Item | Status (✅/🟡/❌) | Evidence (file:line).
Then propose an upgrade plan: the 5–8 highest-impact items, ordered by interview value per hour of work. Each item gets: what changes, the files touched, the estimated size (S/M/L), and the interview talking point it creates ("Now you can say: 'I added integration tests for the payment flow and a CI pipeline that blocks merges on failure.'").
Wait for approval. They can pick a subset.