skills.rest
AndurilCode
AndurilCodeOFFICIAL
Explore all skills by this author →
GitHub

kintsugi

Analyze git history and code patterns to identify undocumented code repairs.

7|2|Updated Mar 5, 2026
Search Tags:#documentation#context engineering#technical debt#git archaeology#change history#codebase audit#workaround recovery
One-click install
npx skills add https://github.com/AndurilCode/craftwork --skill kintsugi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kintsugi
Source: https://github.com/AndurilCode/craftwork/tree/main/plugins/craftwork-professional/skills/kintsugi
Command: npx skills add https://github.com/AndurilCode/craftwork --skill kintsugi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It exposes and documents the missing “why” behind workarounds, defensive patterns, and other past repairs so future developers don’t repeat the same mistakes.

Core Features & Use Cases

  • Scar discovery via git + code patterns: scans commit history and code to identify workaround, guard, magic-value, regression-test, pin, reverted-pattern, silent-migration, and config-override scars.
  • Gold audit (🥇/🥈/⬜ visibility grading): evaluates how well each repair is documented, with evidence-based reconstruction when context is incomplete.
  • Gilding backlog that prioritizes fixes: produces a capped, PR-sized set of documentation improvements (comments, ADRs, test annotations, changelog entries) to restore repair legibility.
  • Health scoring and prevention compass: summarizes overall documentation health and highlights missing process hygiene (templates, incident links, naming conventions, pin discipline).

Quick Start

Run the kintsugi skill against your codebase to generate a repair-visibility report and a prioritized gilding backlog for the most bare or partially documented scars.

Frequently Asked Questions about kintsugi

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

FAQPage Schema
How do I find undocumented workarounds and defensive guards in my codebase?▼

To find undocumented workarounds, you can scan your git history and code patterns to surface invisible repair scars like magic values, pins, and silent migrations. This produces a scar inventory with visibility grading and a prioritized documentation backlog to restore missing context.

Why does our codebase have unexplained defensive guards and workaround patterns?▼

Unexplained defensive guards and workaround patterns occur when past code repairs lack documentation of the original issue. Analyzing commit history reconstructs this missing context, evaluates repair visibility, and generates evidence-based documentation to prevent repeated mistakes.

How do I audit technical debt caused by missing repair documentation?▼

Audit technical debt from missing repair documentation by grading the visibility of past fixes across your codebase. This generates a health score, a prevention compass for process hygiene, and a capped set of PR-sized documentation improvements to address gaps.

Can I generate documentation comments for legacy code fixes using git archaeology?▼

Yes, git archaeology identifies the original context behind legacy code fixes and generates a gilding backlog. This provides PR-sized documentation improvements including code comments, ADRs, test annotations, and changelog entries to restore repair legibility.

What is the best way to prioritize documentation improvements for workaround recovery?▼

The best way to prioritize documentation improvements for workaround recovery is to generate a capped gilding backlog. It ranks bare or partially documented scars to produce PR-sized, documentation-only fixes that restore repair legibility efficiently.

Does this approach work with existing git history and code patterns without extra dependencies?▼

Yes, this approach analyzes existing git history and code patterns directly to identify workaround scars, requiring no external dependencies. It reconstructs missing context evidence-based to evaluate documentation health and highlight missing process hygiene.

Related Skills

Explore More Software Engineering Skills→
marchattonmarchatton
5

git-history-analyzer

Analyze git repository history to trace code origins and contributor patterns.

Community
Intermediate
maltemdmaltemd

writing-code-comments-and-docstrings

Generate inline code comments and docstrings following language-specific conventions.

Community
Intermediate
JylhisJylhis
1

golang-security

Detect Go vulnerabilities using govulncheck, static analysis, and DREAD scoring.

Community
Advanced
mahmoud20138mahmoud20138
10

generate-snapshot

Generate a codebase health snapshot analyzing git history, complexity, debt markers, and dependencies.

Community
Advanced