원클릭으로 Manus에서 모든 스킬 실행

시작하기

quality-guardrails

스타0

포크0

업데이트2026년 7월 19일 19:14

Activate this skill when adding new service endpoints, editing database layers, or preparing to commit changes.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

peterrichards-lr

peterrichards-lr/liferay-ai-commerce-accelerator

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Quality Guardrails & Parity Testing

To prevent regression and ensure 100% architectural integrity, the following automated checks are mandatory:

1. Service Parity Testing

Rule: Every public wrapper method in LiferayService (index.cjs) MUST have a corresponding implementation in either LiferayRestService or LiferayGraphqlService.
Enforcement: Verified via tests/serviceParity.test.cjs. This prevents TypeError: ... is not a function errors when invoking headless wrappers.

2. Startup Step Verification

Rule: Every workflow step registered in a Generator (e.g., [S.CREATE_PRODUCTS]) MUST be mapped to a valid class method.
Enforcement: The BaseGenerator.verifySteps() method is called at boot time in bootstrap.cjs. The microservice will fail to start if any mapping is broken.

3. Pre-Commit Verification

Rule: All code and documentation must be free of syntax errors, undefined references, and lint violations.
Enforcement: Husky and lint-staged run eslint --fix, vitest run, and markdownlint on every commit. This catches ReferenceError, SyntaxError, and documentation drift before they reach the repository.

Last Updated: 2026-07-19 | Last Reviewed: 2026-07-19

이 저장소의 다른 Skills

같은 저장소

coding-standards

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when writing or refactoring microservice and SDK javascript/typescript source files.

2026-07-220

human-in-the-loop

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill before opening pull requests, modifying production configurations, or executing deployment and destructive commands to ensure proper human-in-the-loop verification.

2026-07-220

reflection-and-planning

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when beginning complex tasks, proposing architectural changes, or modifying codebase files to ensure proper planning and predictive failure analysis.

2026-07-220

tool-use-react

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when making tool calls, interacting with the terminal, or invoking GitHub APIs to ensure strict ReAct patterns are followed.

2026-07-220

multi-agent-orchestration

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when delegating tasks, defining subagents, or orchestrating parallel agentic workflows.

2026-07-220

documentation

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill after implementing code changes to verify, review, and update markdown documentation and timestamps.

2026-07-210

name	quality-guardrails
description	Activate this skill when adding new service endpoints, editing database layers, or preparing to commit changes.

Quality Guardrails & Parity Testing

To prevent regression and ensure 100% architectural integrity, the following automated checks are mandatory:

1. Service Parity Testing

Rule: Every public wrapper method in LiferayService (index.cjs) MUST have a corresponding implementation in either LiferayRestService or LiferayGraphqlService.
Enforcement: Verified via tests/serviceParity.test.cjs. This prevents TypeError: ... is not a function errors when invoking headless wrappers.

2. Startup Step Verification

Rule: Every workflow step registered in a Generator (e.g., [S.CREATE_PRODUCTS]) MUST be mapped to a valid class method.
Enforcement: The BaseGenerator.verifySteps() method is called at boot time in bootstrap.cjs. The microservice will fail to start if any mapping is broken.

3. Pre-Commit Verification

Rule: All code and documentation must be free of syntax errors, undefined references, and lint violations.
Enforcement: Husky and lint-staged run eslint --fix, vitest run, and markdownlint on every commit. This catches ReferenceError, SyntaxError, and documentation drift before they reach the repository.

Last Updated: 2026-07-19 | Last Reviewed: 2026-07-19