<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Review on Architect PARK JUN WOO</title><link>https://www.parkjunwoo.com/tags/code-review/</link><description>Recent content in Code Review on Architect PARK JUN WOO</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Apr 2026 13:00:00 +0900</lastBuildDate><atom:link href="https://www.parkjunwoo.com/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Feature Chain — Tracing the full stack with one operationId</title><link>https://www.parkjunwoo.com/tech/feature-chain/</link><pubDate>Fri, 13 Mar 2026 10:00:00 +0900</pubDate><guid>https://www.parkjunwoo.com/tech/feature-chain/</guid><description>Which files do you need to touch to modify a single feature? Feature Chain takes one operationId and automatically extracts the entire scope — API spec, DB schema, authorization policy, state diagram, function implementations, test scenarios, and frontend.</description></item><item><title>whyso — What git blame doesn't tell you</title><link>https://www.parkjunwoo.com/tech/whyso/</link><pubDate>Thu, 12 Mar 2026 10:00:00 +0900</pubDate><guid>https://www.parkjunwoo.com/tech/whyso/</guid><description>git blame tells you who changed what and when. whyso tells you why. A tool that automatically extracts per-file change history from Claude Code session data.</description></item></channel></rss>