사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill quality-gate시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Quality Gate
Run comprehensive code review through the quality gate agent, which orchestrates multiple specialized reviewers based on your project's tech stack.
Config
TECH_STACK = config_read("tech_stack", "generic")
APP_STATUS = config_read("app_status", "development")
LESSONS_PATH = config_read("lessons_path", ".agents/lessons/")bash
DEFAULT_BRANCH=$(git remote show origin | grep 'HEAD branch' | awk '{print $NF}')Arguments
<inputarguments> $ARGUMENTS </inputarguments>
Scope modes:
#123or GitHub URL → PR changes- (no args) → unstaged changes (working directory)
--staged→ staged changes only--branch→ current branch vs default branchpath/to/file ...→ specific files
Step 1: Determine Scope
Parse arguments to determine what code to review:
bash
# Default (unstaged changes)
git diff --name-only --diff-filter=d
# Staged mode
git diff --cached --name-only --diff-filter=d
# Branch mode (use default_branch from Context)
git diff <default_branch>...HEAD --name-only --diff-filter=d
# PR mode
gh pr diff <PR_NUMBER> --name-onlyIf no changes found, report:
## Quality Gate: APPROVED
**Reason:** No changes to review.Step 2: Determine Context Description
Create a context description based on scope:
| Scope | Context Description |
|---|---|
| PR #123 | PR #123: <PR title from gh pr view> |
| --branch | Branch: <current branch name> |
| --staged | Staged changes |
| (no args) | Working directory changes |
| files... | Files: <file list> |
Step 3: Invoke Quality Gate Agent
Launch the quality-gate agent with the determined context:
Task: majestic-engineer:workflow:quality-gate
Prompt: |
Context: <context description from Step 2>
Branch: <branch name or --staged>
Changed files:
<file list>Step 4: Present Results
The quality-gate agent returns a structured verdict. Present the full report to the user.
Verdict outcomes:
- APPROVED - Ready to ship
- NEEDS CHANGES - Fix required issues before shipping
- BLOCKED - Critical issues require immediate attention
Examples
bash
# Review unstaged changes
Skill("quality-gate")
# Review staged changes
Skill("quality-gate") --staged
# Review current branch vs main
Skill("quality-gate") --branch
# Review a PR
Skill("quality-gate") #123
# Review specific files
Skill("quality-gate") app/models/user.rb app/controllers/users_controller.rbConfiguration
Configure reviewers in .agents.yml:
yaml
quality_gate:
reviewers:
- security-review
- pragmatic-rails-reviewer
- performance-reviewerSee CLAUDE.md for available reviewers and configuration options.
