القائمة
Reads and filters production/traces/decision_ledger.jsonl to display a timeline of agent decisions. Supports filtering by agent, risk_tier, task_id, outcome, and date range.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turns real agent failures, repeated prompts, team-specific workflows, and durable project lessons into better SDD skills or memory entries. Use when the user asks to create/update/refine skills, extract reusable lessons, improve skill routing, encode team process, or save patterns for future sessions.
Provides the vendored agent-style v0.3.5 prose rule pack as a portable Claude skill. Use when installing, syncing, applying, or auditing SDD Agent-Style support in another project, or when a style-review workflow needs the bundled rules.
Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.
Scans Markdown (.md) files for malicious code injection including XSS, prompt injection, script injection, obfuscated payloads, and supply chain attack vectors. Use when auditing .md files for security threats or when the user mentions scanning markdown for malicious content.
Provides .NET and ASP.NET Core patterns for REST APIs, Entity Framework, dependency injection, and middleware. Use when working with C# files (*.cs, *.csproj) or when the user mentions .NET, ASP.NET Core, C#, or Entity Framework.
Designs hybrid cloud architectures connecting on-premises infrastructure with public cloud services. Use when designing systems spanning on-prem and cloud, or when the user mentions hybrid cloud or multi-environment architecture.
| name | trace-history |
| description | Reads and filters production/traces/decision_ledger.jsonl to display a timeline of agent decisions. Supports filtering by agent, risk_tier, task_id, outcome, and date range. |
| argument-hint | [--agent <name>] [--risk High|Medium|Low] [--task <task_id>] [--outcome pass|fail|blocked] [--since YYYY-MM-DD] [--last <N>] |
| user-invocable | true |
| allowed-tools | Read, Bash |
| effort | 1 |
| when_to_use | Use to audit why a decision was made, debug a failed task, review high-risk choices, or produce a timeline of agent activity for a session or sprint. |
Read production/traces/decision_ledger.jsonl and display a filtered, human-readable
timeline of agent decisions.
The rendering and filtering logic is implemented in scripts/trace-history.sh.
This skill delegates to that script — do NOT re-implement parsing here.
Invoke exactly once, passing $ARGUMENTS through unchanged:
bash scripts/trace-history.sh $ARGUMENTS
The script handles: flag parsing, filtering, rendering (pretty or JSON), empty-ledger short-circuit, and invalid-argument rejection. Return the script's stdout verbatim to the user.
| Flag | Default | Meaning |
|---|---|---|
--agent <name> | all | Filter by agent_id |
--risk <High|Medium|Low> | all | Filter by risk_tier |
--task <id> | all | Substring match on task_id |
--outcome <pass|fail|blocked|skipped> | all | Filter by outcome |
--since <YYYY-MM-DD> | no limit | Only entries with ts >= date |
--last <N> | 20 | Keep last N after other filters |
--format <pretty|json> | pretty | Output format |
Pretty (default): timeline with risk badges (🔴🟡🟢) and outcome emojis
(✅❌⛔⏭️), grouped with separators and totals. Failed/blocked entries trigger
a /resume-from hint automatically.
JSON: raw matching entries as a JSON array — use when piping to another tool.
The script emits 📭 messages for an empty ledger or zero-match filter. Return
those messages as-is; do not fabricate data.
Agents append one JSON line per significant decision to production/traces/decision_ledger.jsonl.
Append format:
{"ts":"2026-04-16T10:30:00Z","session":"main","agent_id":"backend-developer","task_id":"042","request":"Choose JWT signing algorithm","reasoning":"RS256 supports multi-service verification without sharing secrets","choice":"RS256 over HS256","outcome":"pass","risk_tier":"Medium","duration_s":18}
When to write a ledger entry (per coordination-rules.md Rule 15):
risk_tier Medium or HighLow-risk decisions (trivial style choices, obvious fixes) may be omitted to keep the ledger focused on decisions worth auditing.