ワンクリックでManusで任意のスキルを実行

registration-trace

スター4

フォーク3

更新日2026年4月26日 05:49

Trace the real registration execution path in this hospital project. Use to follow the flow from intent/confirmation through validation, submit lock, DB write, audit, and repair-related code.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

LtAo857

LtAo857/hospital

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Registration Trace

Use this skill when you need to trace the actual registration path in the current repository.

What this skill is for

Answer questions like:

What happens after the user confirms registration?
Where is registration validation done?
Where is the actual write executed?
Where are idempotency, audit, and repair handled?
Which parts are AI orchestration versus core business service logic?

Scope

Focus on the MySQL patient registration flow:

patient-wx-api-mysql
relevant SQL upgrade scripts
related multi-agent execution path

Required reading order

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/controller/RegistrationController.java
patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/service/impl/RegistrationServiceImpl.java
patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/tool/RegistrationAgentTools.java
patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/multi/worker/PolicyAgentWorker.java
patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/multi/worker/ExecutionAgentWorker.java
patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/multi/service/MultiAgentRegistrationAuditService.java
patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/job/MultiAgentRegistrationRepairJob.java
sql/patient_wx_multi_agent_registration_upgrade.sql

Output rules

Separate read/query steps from write/submit steps.
Clearly mark where business validation happens.
Clearly mark where idempotency/locking happens.
Clearly mark where audit and repair/compensation happen.
Use file_path:line_number anchors.

Important project-specific conclusions to verify, not assume

Real registration truth is still in the service layer and database flow, not in the LLM.
Multi-agent execution delegates to the same core registration business capability.
Submit locking is distinct from request throttling.
Audit/repair are extra hardening layers around the multi-agent registration path.

Good response shape

One-sentence summary of the path
Ordered flow from user action to DB write
Validation / lock / audit / repair sections
Key code anchors

このリポジトリの他の Skills

同じリポジトリ

agent-guardrail-check

LtAo857/hospital

Inspect project-specific guardrails in the AI registration flow. Use to verify stage guards, confirmation requirements, request throttling, memory boundaries, idempotency, and fallback behavior.

2026-04-264

doc-code-drift

LtAo857/hospital

Check whether project docs describing AI registration match the current implementation. Use to compare README, docs/agent/*.md, and current multi-agent/rag code for drift.

2026-04-264

multi-agent-map

LtAo857/hospital

Map the current multi-agent registration architecture in this hospital project. Use to explain stage flow, worker responsibilities, coordinator behavior, and where lightweight ReAct is actually used.

2026-04-264

rag-boundary-check

LtAo857/hospital

Verify the real RAG boundaries in this hospital project. Use to confirm knowledge sources, retrieval mode, whether it is explanation-only, and what is intentionally not handled by RAG.

2026-04-264

Registration Trace

Use this skill when you need to trace the actual registration path in the current repository.

What this skill is for

Answer questions like:

What happens after the user confirms registration?

Where is registration validation done?

Where is the actual write executed?

Where are idempotency, audit, and repair handled?

Which parts are AI orchestration versus core business service logic?

Scope

Focus on the MySQL patient registration flow:

patient-wx-api-mysql

relevant SQL upgrade scripts

related multi-agent execution path

Required reading order

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/controller/RegistrationController.java

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/service/impl/RegistrationServiceImpl.java

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/tool/RegistrationAgentTools.java

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/multi/worker/PolicyAgentWorker.java

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/multi/worker/ExecutionAgentWorker.java

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/agent/multi/service/MultiAgentRegistrationAuditService.java

patient-wx-api-mysql/src/main/java/com/example/hospital/patient/wx/api/job/MultiAgentRegistrationRepairJob.java

sql/patient_wx_multi_agent_registration_upgrade.sql

Output rules

Separate read/query steps from write/submit steps.

Clearly mark where business validation happens.

Clearly mark where idempotency/locking happens.

Clearly mark where audit and repair/compensation happen.

Use file_path:line_number anchors.

Important project-specific conclusions to verify, not assume

Real registration truth is still in the service layer and database flow, not in the LLM.

Multi-agent execution delegates to the same core registration business capability.

Submit locking is distinct from request throttling.

Audit/repair are extra hardening layers around the multi-agent registration path.

Good response shape

One-sentence summary of the path

Ordered flow from user action to DB write

Validation / lock / audit / repair sections

Key code anchors

name	registration-trace
description	Trace the real registration execution path in this hospital project. Use to follow the flow from intent/confirmation through validation, submit lock, DB write, audit, and repair-related code.