Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
GitHub 저장소

Praetor

Praetor에는 Harery에서 수집한 skills 2개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.

수집된 skills
2
Stars
2
업데이트
2026-07-09
Forks
0
직업 범위
직업 카테고리 2개 · 100% 분류됨
저장소 탐색

이 저장소의 skills

praetor
소프트웨어 품질 보증 분석가·테스터

Multi-agent production readiness audit. Reads any codebase and produces test cases (unit/integration/security/perf/a11y/chaos), runbooks, alerts, support triage trees, customer comms, compliance mappings (SOC2/GDPR/HIPAA/PCI/WCAG), a secret-scan/secret-lint CI stage, and a consolidated risk register — with file-line traceability. Use this skill whenever a user wants to QA, audit, review, harden, or assess a repo or service for production readiness. Trigger on phrases like "audit my code", "QA review", "readiness check", "find bugs", "security review", "compliance audit", "SOC2 prep", "GDPR audit", "production readiness", "pre-launch review", "risk assessment", "generate runbooks", "write tests for my repo", "harden this service", "what could go wrong in this code", "is this code ready to ship". Also trigger when the user uploads or references a codebase or GitHub repo and asks for a thorough multi-team review even if they don't use the word "Praetor".

2026-07-09
praetor
소프트웨어 개발자

Multi-agent production readiness audit system. 18 expert agent personas across 7 phases serving 5 audiences. Reads any codebase and produces test cases (unit/integration/security/perf/a11y/chaos), runbooks, alerts, support triage trees, customer comms, compliance mappings (SOC2/GDPR/HIPAA/PCI/WCAG), a secret-scan/secret-lint CI stage, and a consolidated risk register — with file-line traceability. Use this skill whenever a user wants to QA, audit, review, harden, or assess a repo or service for production readiness. Trigger on phrases like 'audit my code', 'QA review', 'readiness check', 'find bugs', 'security review', 'compliance audit', 'SOC2 prep', 'GDPR audit', 'production readiness', 'pre-launch review', 'risk assessment', 'generate runbooks', 'write tests for my repo', 'harden this service', 'what could go wrong in this code', 'is this code ready to ship'. Also trigger when the user uploads or references a codebase or GitHub repo and asks for a thorough multi-team review even if they don't use the word

2026-06-15