القائمة
Use when you need the shared DR Platform reference: component verification commands, known repo risk areas, Windows-agent rules, portal checks, and security expectations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.
| name | dr-repo-reference |
| version | 2026-03-26.1 |
| description | Use when you need the shared DR Platform reference: component verification commands, known repo risk areas, Windows-agent rules, portal checks, and security expectations. |
This is the shared reference skill for the repo.
Use it to load the common rules that multiple other skills depend on:
AGENTS.mdTDD_SPEC_FIRST.mdARCHITECTURE.mdSTATUS.mddocs/AGENT_ROLES.mddocs/CODEX_AGENT_POLICY.md.github/context/project-context.mdPortal:
cd portal && go test ./...
cd portal && golangci-lint run ./...
cd portal && go build -o dr-portal .
Agent:
cd dr-agent && GOOS=windows go test ./...
cd dr-agent && GOOS=windows golangci-lint run ./...
cd dr-agent && GOOS=windows GOARCH=amd64 go build -o dr-agent.exe .
Gateway:
cd gateway && go test ./...
cd gateway && go build ./...
Installer:
cd installer && go test ./...
cd installer && go build ./...
Migrations:
When touching portal/, consider:
When touching dr-agent/:
GOOS=windowsWhen changes touch handlers, commands, DB access, sessions, tokens, admin flows, or failover logic, default to security review.
Check for:
When a local runtime check is needed:
docker-compose up -d
docker-compose ps
docker-compose logs --tail=200
Current recurring risks called out by repo docs:
portal/main.goOther DR skills should reference this skill instead of repeating the same repo-wide verification and risk material unless the repetition is necessary for trigger quality.
Role rule:
partner and combatant roles from docs/AGENT_ROLES.md