agent-wrap-ticket

Append ticket learnings to MEMORY.md, decisions.md, and .agentic/context.md.

12|1|Updated Apr 7, 2026

Search Tags:#automation #learnings #pr-workflow #memory.md #context.md #ticket-analysis #decisions.md

Ready to run

npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill agent-wrap-ticket

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-wrap-ticket
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/agent-wrap-ticket
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill agent-wrap-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures per-ticket learnings and appends them to MEMORY.md, decisions.md, and .agentic/context.md (Recent Focus) to preserve knowledge from ticket work. It avoids touching AGENTS.md, qa.md, findings.md, tasks.jsonl, loop-state.json, batch-state.json, or any source/config files, and it soft-fails on errors so it never blocks PR completion.

Core Features & Use Cases

Automatically capture distilled learnings from ticket resolution and persist to project knowledge stores.
Update MEMORY.md, decisions.md, and .agentic/context.md (Recent Focus) with durable entries for cross-ticket reuse.
Works within PR-based ticket workflows to maintain a living knowledge base across episodes.

Quick Start

Activate the wrap-ticket on PR open to extract ticket learnings and append to MEMORY.md, decisions.md, and the recent-focus section of context.

Frequently Asked Questions about agent-wrap-ticket

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

FAQPage Schema

How do I capture per-ticket learnings into project memory files?▼

You can capture per-ticket learnings by appending distilled findings from PR workflows directly into MEMORY.md, decisions.md, and .agentic/context.md. This preserves ticket resolution knowledge for cross-ticket reuse across your project.

What is the best way to automate knowledge persistence in a PR review workflow?▼

Automating knowledge persistence in a PR review workflow involves reading findings_log, qa_md_diff, merged_diff, and conversation_summary to produce durable knowledge entries. The extracted learnings are then appended to project memory files automatically.

Can I use this ticket learning capture without blocking my PR completion?▼

Yes, the ticket learning capture mechanism uses soft-fail semantics to ensure it never blocks PR completion. If errors occur during the knowledge extraction or file appending process, it gracefully fails without interrupting the merge.

How does capturing ticket learnings update my project's context?▼

Capturing ticket learnings updates MEMORY.md, decisions.md, and the Recent Focus section of .agentic/context.md. It strictly avoids touching AGENTS.md, qa.md, findings.md, tasks.jsonl, or any source and config files to maintain workflow integrity.

What limitations exist when appending ticket analysis to memory files?▼

The main limitation is that it writes only to MEMORY.md, decisions.md, and .agentic/context.md. It cannot modify AGENTS.md, qa.md, findings.md, loop-state.json, batch-state.json, or any source files, and it relies on soft-fail behavior to avoid breaking workflows.