skills.rest
alex-quan-001
alex-quan-001COMMUNITY
Explore all skills by this author →
GitHub

tcocp-rca-writer

Draft standardized TCOCP root cause analysis reports from Jira tickets.

Updated Jun 3, 2026
Search Tags:#root cause analysis#jira#rca#incident reporting#tidb cloud#tocp postmortem
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tcocp-rca-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tcocp-rca-writer
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/daily_work/tcocp-rca-writer
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tcocp-rca-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Manually drafting standardized TCOCP (TCOC-Postmortem) root cause analysis reports for TiDB Cloud incidents is time-consuming and prone to formatting errors, missing required fields, and inconsistent timeline documentation. This Skill eliminates that manual work by enforcing strict TCOCP guidelines and auto-populating report sections from source tickets.

Core Features & Use Cases

  • Strict Template Compliance: Enforces all TCOCP formatting rules, including placeholder population, timestamp rounding, severity classification, and prohibited content restrictions (e.g., no cluster IDs in public reports).
  • Context-Aware Population: Automatically pulls incident context from linked Jira TCOC/ST tickets and optional Lark chat history to build accurate event timelines without manual data entry.
  • Guided Workflow: Walks users through a step-by-step process to verify required inputs, fill report sections, and generate the final output file, reducing the risk of missing critical RCA components.
  • Use Case: When a TiDB Cloud oncall engineer needs to submit a postmortem for a cluster incident, use this Skill to generate a fully formatted, compliant RCA report directly from the associated Jira tickets and chat logs in minutes instead of hours.

Quick Start

Use the tcocp-rca-writer skill to draft a TCOCP-styled RCA report for the TCOC ticket PROJ-1234.

Frequently Asked Questions about tcocp-rca-writer

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

FAQPage Schema
How do I generate a TCOCP RCA report for a TiDB Cloud incident?▼

To generate a TCOCP RCA report, provide a Jira TCOC ticket and optional ST ticket or Lark chat history. The Skill automates drafting by pulling incident context and enforcing strict template formatting rules, including timestamp rounding and severity classification.

What is a TCOCP postmortem report and when is it needed?▼

A TCOCP postmortem report is a standardized root cause analysis document required for TiDB Cloud incidents. It is needed when an oncall engineer must submit a compliant RCA report detailing event timelines and severity classifications after a cluster incident.

Can I use Lark chat history and Jira tickets to populate an incident timeline?▼

Yes, you can use Lark chat history and Jira TCOC or ST tickets to populate an incident timeline. The Skill automatically extracts context from these sources to build accurate event timelines without manual data entry.

Does the TCOCP RCA report format restrict specific content like cluster IDs?▼

Yes, the TCOCP RCA report format prohibits specific content such as cluster IDs in public reports. The Skill enforces these strict template compliance restrictions to ensure report safety and formatting consistency.

What is the best way to ensure my incident report meets TCOCP formatting rules?▼

The best way to ensure your incident report meets TCOCP formatting rules is to automate the drafting process. The Skill enforces placeholder population, timestamp rounding, severity classification, and timeline structuring to guarantee compliance.

Why does manual root cause analysis report drafting fail for TiDB Cloud incidents?▼

Manual root cause analysis report drafting fails due to formatting errors, missing required fields, and inconsistent timeline documentation. Automating the process eliminates this manual work and enforces strict TCOCP guidelines.

Related Skills

Explore More Software Engineering Skills→
alex-quan-001alex-quan-001

tcoc-incident-review

Fetch TCOC Jira Incident tickets, classify misclassified ones, and execute batch updates.

Community
Intermediate
oalansilvaoalansilva

incident-postmortem

Draft incident postmortems with timeline, RCA, and action items.

Community
Intermediate
opendatahub-ioopendatahub-io
36

upload-chat-log

Upload chat logs as Markdown files to JIRA tickets.

Official
Intermediate
Amazon-QuickAmazon-Quick
47

incident-postmortem-writer

Generate a blameless incident postmortem report with timeline, impact, root cause, and action items.

Official
Advanced