silver-scan

Scan session logs for unresolved deferred items and unrecorded knowledge.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill silver-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silver-scan
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/silver-scan
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill silver-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospectively surface unresolved deferred items and unrecorded knowledge/lessons from historical session logs, ensuring duplicates are avoided and no context is lost.

Core Features & Use Cases

  • Scan project session logs to identify deferred items and knowledge/lessons.
  • Cross-reference evidence against git history and CHANGELOG to exclude already-addressed items.
  • Present candidates for human approval and file via /silver-add or /silver-rem with a Y/n gating.

Quick Start

Run the silver-scan skill to scan docs/sessions for deferred items and file approved candidates via /silver-add or /silver-rem.

Frequently Asked Questions about silver-scan

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

FAQPage Schema
How do I find unresolved deferred items in project session logs?

To find unresolved deferred items in project session logs, you can scan historical log files to retrospectively surface unrecorded knowledge and filter out already-resolved signals using git history cross-referencing.

What is the best way to deduplicate retrospective knowledge lessons from session logs?

The best way to deduplicate retrospective knowledge lessons is to aggregate candidates across all session logs and cross-reference evidence against git history and CHANGELOG to exclude already-addressed items before presenting them for human approval.

How do I file approved deferred items after scanning session logs?

To file approved deferred items after scanning session logs, review the presented candidates with a Y/n gating mechanism, then file the approved items directly via /silver-add or /silver-rem commands.

Can I scan session logs for knowledge lessons without manually checking git history?

Yes, you can scan session logs for knowledge lessons without manually checking git history because the scanning process automatically cross-references evidence against git history and CHANGELOG to exclude already-addressed items.

What are the limitations when scanning session logs for deferred items?

The main limitation when scanning session logs for deferred items is a 20-item cap per run, requiring multiple runs for larger projects, and all candidates must pass human approval gating before filing via /silver-add or /silver-rem.