taw-trace

Query git commit history and blame via taw-kit with scope, phase, file, or feature queries.

32|13|Updated Apr 21, 2026

Search Tags:#git #commit #translation #history #blame #taw-kit #vn

Ready to run

npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-trace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taw-trace
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-trace
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-dev users often need to answer questions about when changes happened in a taw-kit project, which commit introduced a feature, or which phase a change belongs to. This skill provides a single, easy-to-use interface over git log / git blame, translating SHAs into plain prose in the user's language (Vietnamese by default for VN users).

Core Features & Use Cases

Look up commits and blame information by scope, phase, file, or feature.
Translate SHAs into friendly, readable prose for quick understanding.
See changes across phases and track when a feature/bugfix was introduced in the codebase.

Quick Start

Ask taw-trace to show history for a scope like "auth" or a phase like "P2", or a file like "app/login/page.tsx", or a feature slug like "tiktok-shop".

Frequently Asked Questions about taw-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check git commit history without knowing git commands?▼

You can check git commit history without knowing git commands by querying a wrapper that translates git log and blame data into readable prose. This allows non-developers to trace code changes directly without memorizing syntax.

Can I look up which commit introduced a feature in a specific file?▼

Yes, you can look up which commit introduced a feature by querying history based on a specific file, feature slug, phase, or scope. The wrapper maps SHAs to human-friendly descriptions for quick understanding.

Does git blame work for tracking changes across project phases?▼

Git blame works for tracking changes across project phases by supporting phase-based queries like P2. It returns branded, readable results in the user's language, mapping SHAs to plain prose for non-developers.

What is the best way to trace code changes for a specific scope like auth?▼

The best way to trace code changes for a specific scope like auth is to use a taw-kit wrapper that queries git history by scope. It translates commit SHAs into plain prose, returning readable results in the user's language.

Do I need git know-how to understand blame information and commit history?▼

You do not need git know-how to understand blame information and commit history. The skill queries git using a taw-kit wrapper and translates SHAs into plain prose in the user's language, defaulting to Vietnamese for VN users.