sage-knowledge-hygiene

Included with Lifetime

$97 forever

Evaluate and maintain knowledge freshness - detect and fix stale knowledge

Code Review

What this skill does


# Knowledge Hygiene

When knowledge is recalled, evaluate its freshness. Stale knowledge injects wrong context.

## Staleness Signals

| Signal | How to Detect | Example |
|--------|---------------|---------|
| **Version mismatch** | Knowledge mentions old version | "Post v2.4" when we're on v2.6 |
| **Temporal markers** | "TODO", "planned", "upcoming", "will be" | Feature listed as TODO but shipped |
| **Contradiction** | Recalled content conflicts with current facts | "Not implemented" but we just used it |
| **Date references** | Specific dates in the past | "Q1 2025 roadmap" |

## Type-Specific Evaluation

Different knowledge types decay differently:

| Type | Decay Rate | Evaluate For |
|------|------------|--------------|
| `knowledge` | Medium | Version refs, temporal markers, contradictions |
| `preference` | Very slow | Only explicit user contradiction |
| `todo` | Fast | Completion, age without action (30+ days) |
| `reference` | Slow | Source validity, version refs |

## When to Evaluate

1. **On recall** - Quick scan when knowledge is surfaced
2. **Session start** - Review proactively recalled items
3. **After version bump** - Check for version-specific knowledge
4. **Explicit request** - User asks to review knowledge

## Remediation Actions

### If content is wrong/outdated:
```python
sage_update_knowledge(
    knowledge_id="the-id",
    content="Updated accurate content",
)
```

### If superseded but worth keeping for history:
```python
sage_deprecate_knowledge(
    knowledge_id="the-id",
    reason="Superseded by v2.6 skills architecture",
    replacement_id="new-knowledge-id",  # optional
)
```

### If no longer relevant:
```python
sage_archive_knowledge(knowledge_id="the-id")
```

### If still valid (bump freshness):
```python
sage_update_knowledge(
    knowledge_id="the-id",
    content=None,  # Keep content
    # Just accessing it updates last_recalled internally
)
```

## Quick Hygiene Check

When you see recalled knowledge, ask:

1. **Version check**: Does it reference an old version?
2. **Completion check**: Does it list something as TODO that's done?
3. **Contradiction check**: Does it conflict with what we know now?

If any answer is yes -> remediate immediately.

## Example: Stale Feature List

Recalled knowledge says:
> "Post v2.4.0 - TODO: Proactive recall on session start"

But we're on v2.6 and proactive recall shipped in v2.5.

**Action:**
```python
sage_update_knowledge(
    knowledge_id="feature-ideas",
    content="Updated content marking proactive recall as shipped...",
)
```

Files: 1

Size: 2.8 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/b17z/sage/tree/main/skills/sage-knowledge-hygiene

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts