enrich

Gather and synthesize factual context from Jira, GitHub, AWS, and Datadog into structured briefings.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/mslshao/claude-harness --skill enrich-mslshao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enrich
Source: https://github.com/mslshao/claude-harness/tree/main/project-tier/skills/enrich
Command: npx skills add https://github.com/mslshao/claude-harness --skill enrich-mslshao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand a Jira ticket, GitHub PR, or loosely defined topic by gathering scattered context into one factual briefing. It reduces the time spent jumping between issue trackers, code, cloud service state, and observability tools before analysis, meetings, or handoffs.

Core Features & Use Cases

  • Multi-source context gathering: Pulls structured details from Jira, GitHub PRs, AWS, Datadog, and the local codebase when relevant.
  • Structured factual briefings: Produces a concise summary, attributed findings, codebase references, and open questions without drifting into recommendations.
  • Parallel evidence collection: Runs independent lookups in parallel after the primary source is identified to minimize wait time.
  • Use cases: Use it to brief yourself on a ticket before debugging, understand what a PR changes before review, prepare for a meeting about a service issue, or load code and runtime context for an unfamiliar topic.

Quick Start

Ask the AI to use the enrich skill on a Jira ticket like MX2-12345, a PR like #456, or a topic such as payment retries.

Frequently Asked Questions about enrich

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

FAQPage Schema
How do I get a quick briefing on a Jira ticket and GitHub PR before a meeting?

To get a quick briefing on a Jira ticket or GitHub PR, you can gather and synthesize factual context into a structured summary. This process pulls structured details from issue trackers, pull requests, AWS, Datadog, and the local codebase when relevant.

How do I gather context for codebase orientation and ticket triage?

You gather context for codebase orientation and ticket triage by parsing identifiers and retrieving primary-source details. The system applies bounded codebase reading and parallel AWS and Datadog lookups to produce a concise factual summary with attributed findings.

Can I use context loading to understand what a GitHub PR changes before review?

Yes, you can use context loading to understand what a GitHub PR changes before review. It retrieves primary-source details and runs bounded codebase reading to synthesize codebase references and factual findings into a structured briefing for quick analysis.

Does enrich work with AWS and Datadog for service investigation?

Yes, enrich works with AWS and Datadog for service investigation by running parallel lookups alongside primary-source retrieval. It gathers runtime context and cloud service state to help you load code and runtime context for an unfamiliar topic or service issue.

What happens if AWS or Datadog systems are unavailable during context gathering?

If AWS or Datadog systems are unavailable during context gathering, the process applies graceful handling to continue synthesizing factual context. It still produces a structured briefing with attributed findings and open questions from available primary sources like Jira and GitHub.