Back to Details

tk-ask-repo

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Answering Repository Questions

处理代码仓库查询

Handle only concrete repository questions explicitly invoked through 
/tk-ask-repo
, 
$tk-ask-repo
, or host skill selection.
This is a read-only investigation that does not modify source, tests, configuration, artifacts, history, or remote state. It does not own implementation, closing user decisions, runtime estimation, or real-browser reproduction.
仅处理通过
/tk-ask-repo
、
$tk-ask-repo
或主机技能选择明确发起的具体仓库问题。
本次调查为只读性质，不会修改源代码、测试用例、配置文件、制品、历史记录或远程状态。 不负责代码实现、用户决策落地、运行时长估算或真实浏览器环境复现。

🔴 CHECKPOINT · 🛑 STOP · Investigation boundary

🔴 检查点 · 🛑 停止 · 调查边界

Do not implement, mutate, or turn incomplete evidence into a repository claim; when an anchor or evidence path cannot be established, stop with 
Status: Unverifiable
.
请勿进行代码实现、修改操作，或基于不完整证据做出仓库相关断言；当无法确定锚点或证据路径时，需以
Status: Unverifiable
终止调查。

User Experience

用户体验

Keep the internal investigation rigorous, but present the result as a natural explanation rather than a report.
  • State the answer to the question first.
  • Explain the value or behavior flow in an order that is easy to understand.
  • Place 
    path:line
    evidence next to each important repository claim.
  • Do not show internal classifications, checkpoints, or search ledgers by default.
  • Use short prose or a limited list unless a comparison truly requires a table.
  • Explain interactively one step at a time only when the user says “하나씩 따라가며 설명해줘”.
内部调查需严谨，但呈现结果时应采用自然易懂的说明而非报告形式。
  • 首先直接给出问题答案。
  • 以易于理解的顺序解释数值或行为流程。
  • 在每个重要的仓库断言旁附上
    path:line
    证据。
  • 默认不展示内部分类、检查点或搜索记录。
  • 除非对比确实需要表格，否则使用简短文字或有限列表。
  • 仅当用户提出“请一步步讲解”时，才逐步交互式解释。

Investigation Principles

调查原则

Use the question’s visible string, identifier, path, address, or symbol as the first anchor. If there is no anchor, briefly explain the searches attempted and the information needed, then end with 
Status: Unverifiable
.
Every repository-state claim must have one of the following:
  • An exact 
    path:line
    or current-state evidence
  • An explicit limitation that the evidence cannot be read
  • A clear indication that the explanation is an 
    inference
    when judgment is required
A declaration proves only shape. When asked about a value’s origin, trace the actual assignment, stored input, transformation, and external boundary.
Do not turn 
not found
directly into 
absent
. Check the current baseline, relevant in-progress changes, conditional paths, and possible dynamic connections.
For impact questions, investigate related read and write locations and distinguish:
  • Consumers that must change
  • Consumers that must not change
  • Consumers that cannot be determined due to insufficient evidence
When asked about ownership, check consuming-side transformations, permissions, feature conditions, conditional rendering, and environment differences before blaming the producer.
以问题中的可见字符串、标识符、路径、地址或符号作为首个锚点。 若没有锚点，需简要说明尝试过的搜索方式及所需信息，然后以
Status: Unverifiable
结束。
所有关于仓库状态的断言必须满足以下条件之一：
  • 具备精确的
    path:line
    或当前状态证据
  • 明确说明无法读取证据的限制
  • 当需要判断时，清晰标注该说明为
    inference
    （推论）
声明仅能证明结构形态。 当被问及数值来源时，需追踪实际赋值、存储输入、转换过程及外部边界。
请勿直接将“未找到”判定为“不存在”。 需检查当前基线、相关进行中的变更、条件分支及可能的动态关联。
对于影响范围类问题，需调查所有相关的读写位置，并区分：
  • 必须修改的消费者
  • 不得修改的消费者
  • 因证据不足无法确定的消费者
当被问及责任归属时，在归咎于生产者之前，需检查消费者侧的转换逻辑、权限、功能条件、条件渲染及环境差异。

Representative Traces

典型追踪路径

Value Origin

数值来源

text
표시 값
→ 바인딩
→ 소비 표현식
→ 전달 필드
→ 타입/스키마
→ 변환
→ 실제 대입 또는 외부 경계
text
显示值
→ 绑定
→ 消费表达式
→ 传递字段
→ 类型/模式
→ 转换
→ 实际赋值或外部边界

Structure

结构流程

text
진입점
→ 화면/호출자
→ 전달 경계
→ 생산자
→ 저장소 또는 외부 시스템
text
入口点
→ 页面/调用方
→ 传递边界
→ 生产者
→ 仓库或外部系统

Existence

存在状态

현재 기준선, 관련 진행 중 변경과 실제 연결 상태를 근거로 
없음 | 아직 반영되지 않음 | 자리만 있음 | 실제 사용 중
의미를 구분합니다.
基于当前基线、相关进行中的变更及实际连接状态，区分「不存在 | 尚未生效 | 仅占位 | 实际使用中」的含义。

Impact and Ownership

影响范围与责任归属

Check all relevant consumers and explain which parts cause the current issue and which parts must be preserved.
检查所有相关消费者，说明哪些部分导致当前问题，哪些部分必须保留。

When the Question Is Out of Scope

超出范围的请求

Do not keep investigating to force an answer for these requests:
  • Code implementation or commits
  • User decisions about product behavior
  • Real-browser reproduction
  • Schedule or day-level estimates
  • General knowledge unrelated to the repository
When possible, state the appropriate next action in one sentence. Route general implementation to the current executor without requiring a specific TigerKit skill. Use 
tk-prep
when the work must first be specified, or 
tk-browser-verify
when real-browser evidence is required.
对于以下请求，请勿继续调查以强行给出答案：
  • 代码实现或提交
  • 关于产品行为的用户决策
  • 真实浏览器环境复现
  • 日程或按天估算的时长
  • 与仓库无关的通用知识
若可能，用一句话说明合适的后续操作。 将通用实现需求转交给当前执行者，无需指定特定TigerKit技能。 当工作需要先明确需求时使用
tk-prep
，当需要真实浏览器证据时使用
tk-browser-verify
。

Response Format

响应格式

Do not begin with a fixed 
Answer
, 
Evidence
, 
Origin
report. Put the most direct answer to the question in the first paragraph.
Then explain only as much flow, impact, and limitation as needed. Place important evidence next to the corresponding explanation.
Always end the response with 
## 공유용 요약
.
공유용 요약은:
  • 3~10
    줄
  • 본문에서 이미 검증된 사실만 사용
  • 새로운 추론이나 새 결론을 만들지 않음
  • 코드 내부 상세보다 결론, 영향, 책임 경계 중심
  • 타팀, 기획, 백엔드, 리뷰어에게 그대로 전달할 수 있는 자연스러운 문장
조사가 실패한 경우에도 확인된 사실이 있다면 공유 가능한 범위만 요약하고, 확인되지 않은 내용은 확인되지 않았다고 명시합니다.
请勿以固定的「Answer」「Evidence」「Origin」报告开头。 将最直接的问题答案放在第一段。
然后仅解释必要的流程、影响及限制。 将重要证据附在对应的说明旁。
必须以
## 共享用摘要
结尾。
共享用摘要需满足：
  • 3~10行
  • 仅使用正文中已验证的事实
  • 不得添加新推论或新结论
  • 重点关注结论、影响、责任边界，而非代码内部细节
  • 语句自然流畅，可直接传达给其他团队、策划、后端或评审人员
即使调查失败，若有已确认的事实，仅对可共享的范围进行摘要，未确认的内容需明确标注为未确认。