skills.rest
RebelliousSmile
RebelliousSmileCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

taste

Detect outdated content in documentation and source code against a live codebase.

1|Updated Mar 3, 2026
Search Tags:#code quality#code analysis#document review#dependency detection#content obsolescence
One-click install
npx skills add https://github.com/RebelliousSmile/my-claude-marketplace --skill taste-rebellioussmile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taste
Source: https://github.com/RebelliousSmile/my-claude-marketplace/tree/main/plugins/overcode/skills/taste
Command: npx skills add https://github.com/RebelliousSmile/my-claude-marketplace --skill taste-rebellioussmile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps users identify outdated information in their documentation and code, ensuring that projects remain up-to-date and maintainable.

Core Features & Use Cases

  • Document Assessment: Extracts and verifies claims in markdown files against the codebase, providing an ordered fix plan.
  • Code Assessment: Detects deprecated imports, broken relative imports, removed function calls, rule violations, and stale TODO/FIXME comments.
  • Use Case: When reviewing a codebase or documentation, use the 'taste' command to scan for outdated patterns and ensure that all references and dependencies are current.

Quick Start

Use the /taste command followed by the file path to check for obsolescence. For example, /taste path/to/file.md

Frequently Asked Questions about taste

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

FAQPage Schema
How do I detect obsolete content in markdown documentation against a live codebase?▼

To detect obsolete content in markdown documentation, you can scan files to extract and verify claims against your live codebase. This process identifies outdated references and generates an ordered fix plan to maintain document accuracy.

How do I find deprecated imports and stale TODO comments during code analysis?▼

Finding deprecated imports and stale TODO comments is achieved by scanning source code for removed function calls, broken relative imports, and outdated fixme tags. This code analysis flags rule violations to help you clean up stale codebase artifacts.

Does document obsolescence detection work with multiple file types?▼

Yes, document obsolescence detection supports multiple file types. It requires specific rules and patterns to accurately identify and report outdated information across both documentation and source code files.

What's the best way to identify broken relative imports and removed function calls in source code?▼

The best way to identify broken relative imports and removed function calls is to perform automated code assessment against your project. This detects deprecated dependencies and rule violations, ensuring your source code references remain current.

How do I scan for outdated patterns and ensure dependencies are current?▼

You can scan for outdated patterns by running a targeted check command followed by your target file path. This verifies extracted claims and dependencies against the live codebase, ensuring all references are current and providing an ordered fix plan.

Related Skills

Explore More Software Engineering Skills→
willdadywilldady
63

docs-audit

Audit documentation claims against source code and git history.

Community
Advanced
NSEvteevNSEvteev
31

links-validate

Validate and fix broken links between Markdown documents.

Community
Intermediate
alangebalangeb

code-review-workflow

Run pyscan, pyanalyze, ruff, and black to generate a unified markdown report.

Community
Intermediate
nobelknobelk

security-scan

Identify security vulnerabilities in codebases via manual review and automated pattern detection.

Community
Advanced