review-and-qa

The review-and-qa skill is an automated engineering assistant designed to maintain the high standards of the Storyblok monorepo and its associated SDKs. It provides a structured, two-phase evaluation process for any commit, branch, or pull request. The first phase focuses on static code analysis, ensuring that the changes are architecturally sound, secure, and follow the project's established conventions. By enforcing a standardized PR checklist, this skill helps developers identify common pitfalls such as secrets exposure, lack of documentation, or suboptimal design patterns early in the development lifecycle.

The second phase transitions into Quality Assurance (QA) planning. It generates detailed, manual test cases tailored to the specific changes, covering the happy path, negative scenarios, edge cases, and error recovery procedures. This systematic approach ensures that functionality is validated across different environments, including Storyblok's JavaScript, React, Vue, and Astro SDKs.

• Automated Code Review: Analyzes code structure, naming conventions, and adherence to DRY principles.

• Security Compliance: Checks for potential injection vulnerabilities and the unintentional inclusion of sensitive tokens or credentials.

• PR Checklist Enforcement: Validates that every pull request includes necessary tests, documentation updates, and appropriate migration notes for breaking changes.

• QA Test Plan Generation: Produces actionable test suites based on templates, ensuring full coverage of normal operations and complex edge cases.

• Architectural Validation: Ensures that new code integrates seamlessly with existing Storyblok modules, utility helpers, and centralized constants.

• Dependency Management: Evaluates new third-party dependencies for license compatibility, maintenance status, and bundle size impact.

• Users should trigger this skill by providing a target commit hash, branch name, or PR reference as the primary argument.

• The output is provided in markdown format, categorizing issues by severity level (Critical, Major, Minor) with direct references to file paths and specific lines of code.

• The skill assumes the project follows standard repository patterns found in Storyblok's ecosystem (e.g., packages/cli, packages/js-client).

• Developers should utilize the generated test plans as a starting point for manual regression testing and cross-browser validation.

• Constraints include internet-accessible repository visibility and adherence to conventional commit standards for release notes.