skills.rest
Harshodai
HarshodaiCOMMUNITY
Explore all skills by this author →
GitHub

tayari-failure-archaeology

Document root causes and lessons from past technical failures in the Tayari Skill Boost repository.

Updated Jan 20, 2026
Search Tags:#debugging#documentation#troubleshooting#post-mortem#engineering#knowledge-base
One-click install
npx skills add https://github.com/Harshodai/tayari-skill-boost --skill tayari-failure-archaeology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tayari-failure-archaeology
Source: https://github.com/Harshodai/tayari-skill-boost/tree/main/.claude/skills/tayari-failure-archaeology
Command: npx skills add https://github.com/Harshodai/tayari-skill-boost --skill tayari-failure-archaeology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the repetition of past engineering mistakes and wasted effort by providing a centralized, verified chronicle of resolved bugs, dead ends, and architectural lessons within the Tayari Skill Boost platform.

Core Features & Use Cases

  • Historical Context: Access a curated record of major investigations, including nil-pointer panics, CI/CD drift, and infrastructure migrations.
  • Decision Guardrails: Quickly verify if a perceived bug is a known issue or a deliberate design choice before initiating a fix.
  • Use Case: Before attempting to "fix" a failing test or a port configuration, consult this Skill to see if the issue is a documented "DOC-DRIFT" or a known "WON'T-FIX" scenario, saving hours of redundant debugging.

Quick Start

Use the tayari-failure-archaeology skill to search for known issues related to the current bug symptom before starting any investigation.

Frequently Asked Questions about tayari-failure-archaeology

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

FAQPage Schema
What is the best way to find out if a failing test is a known issue or a deliberate design choice?▼

Consulting failure documentation provides decision guardrails to verify if a failing test is a known WON'T-FIX scenario or a documented DOC-DRIFT issue, confirming whether it is a deliberate design choice before initiating a fix.

Why does a port configuration issue keep recurring after infrastructure migrations?▼

Recurring port configuration issues after infrastructure migrations are often documented within the historical context of this chronicle, capturing architectural lessons and resolved bugs to prevent the repetition of past engineering mistakes.

Do I need access to the repository's internal chronicle to troubleshoot nil-pointer panics?▼

Yes, troubleshooting nil-pointer panics requires access to the repository's internal chronicle to cross-reference current symptoms against established project history and review documented evidence from previous system incidents.

When should I not use post-mortem documentation for troubleshooting CI/CD drift?▼

Post-mortem documentation for troubleshooting CI/CD drift should not be used when encountering undocumented edge cases or scenarios outside the Tayari Skill Boost repository, as it only covers verified historical records within that specific platform.

Related Skills

Explore More Software Engineering Skills→
dd-xiaozhidd-xiaozhi
2

adr

Record and manage architectural decision documents in a Markdown repository.

Community
Intermediate
tankygranny05tankygranny05
2

debug-session-documenter

Generate structured post-mortem reports documenting debugging sessions and lessons learned.

Community
Advanced
TalonT-OrgTalonT-Org
5

diagnose-ci

Fetch CI logs for a failing Git branch and classify failure types.

Official
Intermediate
haizhouyuanhaizhouyuan

digest-content

Convert articles, transcripts, or reports into structured Markdown digests.

Community
Advanced