skills.rest
0xAndoroid
0xAndoroidCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

techdebt

Extract session learnings and triage tech debt into CLAUDE.md.

Updated Aug 23, 2026
Search Tags:#code quality#documentation#knowledge management#claude.md#tech debt#triage#session review
One-click install
npx skills add https://github.com/0xAndoroid/dotfiles --skill techdebt-0xandoroid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/0xAndoroid/dotfiles/tree/main/claude/skills/techdebt
Command: npx skills add https://github.com/0xAndoroid/dotfiles --skill techdebt-0xandoroid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session sweep: persist learnings to CLAUDE.md, fix small debt, and surface larger debt for user decision.

Core Features & Use Cases

  • Phase 1: Gather Session Context — Review conversation, changes, and relevant files.
  • Phase 2: Persist Learnings → CLAUDE.md — Integrate non-obvious learnings into CLAUDE.md without duplicating entries.
  • Phase 3: Tech Debt Triage — Identify maintainability issues and surface actionable improvements with rationale.

Quick Start

Review the session and run this skill to update CLAUDE.md with key learnings and triage notes.

Frequently Asked Questions about techdebt

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

FAQPage Schema
How do I document session learnings and capture tech debt at the end of a coding session?▼

To document session learnings and capture tech debt, you can run an end-of-session sweep that extracts non-obvious learnings into CLAUDE.md and triages maintainability issues. This preserves contextual knowledge and surfaces actionable architectural improvements with rationale.

What is the best way to persist contextual knowledge from a coding session into a knowledge base?▼

The best way to persist contextual knowledge is to integrate non-obvious session learnings directly into a CLAUDE.md file. This acts as a persistent knowledge base, consolidating conversation context and code changes without duplicating existing entries.

How does tech debt triage work when reviewing code changes across a project?▼

Tech debt triage works by reviewing the session's conversation and modified files to identify maintainability issues. It separates small debt that can be fixed immediately from larger architectural debt, surfacing the larger issues for user decision with actionable rationale.

Do I need a CLAUDE.md file to manage code quality and session documentation?▼

Yes, you need a CLAUDE.md file to manage code quality and session documentation with this process. It serves as the required knowledge base where session learnings and tech debt triage notes are permanently persisted across your codebase.

Can I use this end-of-session sweep for architectural triage across multiple teams?▼

Yes, you can use this end-of-session sweep for architectural triage across codebases and teams. It consolidates knowledge and identifies maintainability issues, making it suitable for software projects requiring post-session documentation and broader architectural review.

Related Skills

Explore More Software Engineering Skills→
YuvaseeYuvasee
10

learn

Extracts and generalizes session learnings into a CLAUDE.md file using Git.

Community
Intermediate
zeropoint-foundationzeropoint-foundation
1

tech-debt-tracker

Extract, classify, and persist technical debt from conversations and PR reviews.

Community
Advanced
rodmena-limitedrodmena-limited
3

moai-foundation-claude

Create, configure, and manage Claude Code Skills with templates and tools.

Official
Advanced
barkleesandersbarkleesanders
5

file-todos

Create and track file-based todos for code review feedback and technical debt.

Community
Intermediate