ShipCheck

ShipCheck is a preflight checker for hackathon submissions. You paste a public GitHub repo URL and it checks the things submission announcements actually demand: the repo is public, a license is there, a README is there, the planning docs are there, and a demo or live link a reviewer can open. You get a pass/fix list and one short summary of what to fix first. It is for solo builders in the last hour before a deadline, which is where I live. I built it because I nearly lost an entry this week to a rule buried in an announcement. What I learned: write the acceptance example first. The whole build was verified against one expected output, and that is what caught the one real bug before it shipped. I installed the pack with npx skills add challengepost/learn-ai-basics --all -y in a fresh empty folder and ran the stages in order. 1-start wrote my learner profile from the concept I brought in. 2-scope sharpened it into scope.md: one page, five checks, no accounts, no scoring. 3-prd turned that into prd.md with the full core journey and the error states. 4-spec made the technical call in spec.md: a zero-dependency Node server, the public GitHub API, and a free text service for the summary with a rule-based fallback behind it. 5-build split it into three slices in checklist.md, the five verdicts first, then the summary, then the error states, and each slice was verified against real repos and committed before the next started. 6-ship is this step: public repo, live instance, demo video, submission. The docs the skills generated are in the repo, in devpost/ and at the root.