Use this checklist before publishing or releasing pet-forge.
Audit the repository as a standalone open-source toolkit for building SVG/APNG desktop pets. The public repository must not depend on private local paths, private project checkouts, personal accounts, or unpublished assets.
-
Personal information
- No personal names, nicknames, handles, email addresses, local usernames, or private machine paths.
- No references to private directories such as Windows drive paths or user home directories.
-
Repository usability
- README quick start commands run from the paths shown.
routes/apng/tools/package.jsondeclares all Node dependencies..env.examplecontains only placeholder keys and no real secrets.- Generated files,
node_modules,.env, and caches are ignored.
-
Documentation consistency
- README, SKILL, CLAUDE, route docs, and shared docs describe the same SVG/APNG split.
- State counts and A/B/C loop classifications match
routes/apng/prompts/template.js. - No document claims a private source file is available to public users.
-
License boundary
- Public docs distinguish reusable methodology/tools from any private product assets.
- Copied or adapted code keeps appropriate attribution and license notes.
-
Tool entry points
node gen-video.jsprints help without missing modules.node gen-images.js --listprints the state list.node test-api.jshandles missing API keys gracefully.- Python helper scripts print
--helpwithout importing project-specific paths.
Report findings in this order:
- Must Fix: privacy leaks, secrets, broken quick start, incorrect license claims.
- Should Fix: confusing public docs, stale private-project references, unclear commands.
- Verified: commands and files checked successfully.