Skip to main content
Manusで任意のスキルを実行
ワンクリックで
GitHub リポジトリ

Praetor

Praetor には Harery から収集した 2 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 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