원클릭으로
sleuth
When asked to sleuth or investigate production data or a customer support issue, follow these rules
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
When asked to sleuth or investigate production data or a customer support issue, follow these rules
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Draft a consistent, well-structured PR title and description by analyzing the Linear issue's title and full branch diff
Turn a task into an agent-ready Linear ticket — either by fleshing out an existing ticket or by drafting and filing a new one. Investigates the codebase, settles open decisions via clarifying questions, and produces a ticket a fresh agent with no shared context can execute unassisted.
When asked to "push a PR" or "create a PR", always push and create a draft PR on github
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree, and then implementing the plan in reviewable bite-sized chunks one step at a time. Use when user wants to stress-test a plan, get grilled on their design, mentions "grill me", "make a plan", etc.
SOC 직업 분류 기준
| name | sleuth |
| description | When asked to sleuth or investigate production data or a customer support issue, follow these rules |
When asked to sleuth or investigate a customer support or Help Scout issue, you MUST follow these rules:
You CANNOT access production data, but I can run psql queries for you and report back
You CANNOT access production iex console, but I can run elixir function calls for you and report back
You MUST ONLY suggest read-only queries and function calls
You MUST NEVER suggest any query or call that is destructive in any way