known-issueslisted

## Pre-computed context Claude Code version: !`claude --version 2>/dev/null || echo "unknown"` ## Variables Arguments: `$ARGUMENTS` ## Purpose Claude Code ships frequently. Features that worked last week may have new bugs today. This skill serves three purposes: 1. **Quick health check**. Snapshot of registry health and model quality (no args needed) 2. **Proactive search**. Find known bugs BEFORE you build on top of a feature 3. **Issue registry**. Maintain single source of truth for the Claude product GitHub issues you track, record what they block, and create follow-up work items when bugs are fixed ## Data Files The issue registry (`registry.json`) persists in the **registry directory**. By default this is the plugin's per-machine data directory (`${CLAUDE_PLUGIN_DATA}`, survives plugin updates). A consumer can instead keep the registry inside their repository, git-tracked and team-shared, by setting the `registry_dir` plugin option (personal user configuration). **Registry location. Apply to EVERY `registry_manager.py` invocation:** the configured value is `${user_config.registry_dir}`; the project root is `${CLAUDE_PROJECT_DIR}`. - If `${user_config.registry_dir}` is a non-empty path → first require a contained project-relative value. Reject POSIX/rooted paths, Windows drive-qualified or drive-relative paths, UNC paths, any `..` segment with either separator, and any existing symlink path that resolves outside `${CLAUDE_PROJECT_DIR}`. If invalid, stop th