Explicit retrospective of a coding session with evidence-backed suggestions for future work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Review the current coding session by default. Review another session only when the user specifies it and the evidence is accessible. Use the available writing-for-agents guidance when suggesting agent instructions.
Reviewers may need to inspect code and history to understand a change; do not assume a diff is enough. Treat mechanical checks, rules, and documentation as options whose costs must be justified by the observed failure.
This is a read-only suggestion workflow. Present proposed changes in chat; edit AGENTS.md, code, CI, memory, or issues, send messages, and start background tasks only when separately authorized. Existing explicit authorization remains effective.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.