gsp-project-review

To validate codebase implementation against design intent, cross-reference your BUILD-LOG.md claims and git diff with project design chunks. This surfaces mismatches between design artifacts and built components so teams can decide if a build is shippable or needs revision.

A design system QA review verifies token usage, component coverage, and imagery style against brand pattern files. It performs token audits and searches for hardcoded values to ensure the actual codebase implementation aligns with the established brand system.

To check for hardcoded values and verify accessibility, run Grep and Glob searches across the codebase and reference prior audits. This identifies skipped design tokens and accessibility issues, producing an actionable issues list for remediation.

Yes, you can automate the design review process by spawning a reviewer agent that reads BUILD-LOG.md and runs git diff. The agent applies a structured methodology to verify changed files and generate acceptance reports without manual intervention.

From a codebase design alignment review, you get an acceptance-report.md, an issues.md file, and an INDEX.md written to your project's review directory. These deliverables document coverage checks, accessibility status, and actionable mismatches.

To cross-reference build claims with actual git changes, read the BUILD-LOG.md file and execute a git diff. This confirms which files were actually changed and whether the build produced the artifacts claimed by the developer.