skills.rest
mbwsims
mbwsimsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

discover

Detect hidden code conventions and generate evidence-backed rule suggestions.

71|7|Updated Apr 4, 2026
Search Tags:#automation#code analysis#codebase#sampling#convention detection#rule generation
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill discover-mbwsims
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/discover
Command: npx skills add https://github.com/mbwsims/claude-universe --skill discover-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers often work with unwritten conventions that are not captured in instruction files, leading to inconsistent code and hidden bugs.

Core Features & Use Cases

  • Automatic convention detection across import styles, naming, error handling, and architecture boundaries.
  • Evidence‑backed rule suggestions with sample counts and file paths.
  • Focused analysis by specifying a focus area such as imports, testing, or API patterns.
  • Quick integration with CLAUDE.md or .claude/rules/ to enforce discovered conventions.

Quick Start

Ask the discover skill to analyze the project and list the top conventions you want to capture.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I detect unwritten code conventions across a codebase?▼

Detecting unwritten code conventions requires sampling source files to analyze import styles, naming, error handling, and architecture boundaries, then generating evidence-backed rule suggestions with file paths and sample counts.

How do I generate instruction file rules from existing project patterns?▼

Generating instruction file rules involves scanning existing project code to extract hidden conventions, producing clear, evidence-backed rule suggestions that can be integrated directly into instruction files like CLAUDE.md or .claude/rules/.

Can I focus convention detection on specific areas like API patterns or testing?▼

Yes, convention detection can be focused by specifying a target area such as imports, testing, or API patterns, allowing the analysis to concentrate on specific coding styles and architectural boundaries.

Do I need external dependencies to analyze codebase conventions?▼

No external dependencies are required to analyze codebase conventions; the process requires only read access to source files and the ability to grep and sample files to extract hidden patterns.

What is the best way to extract hidden coding rules for developer instruction files?▼

The best way to extract hidden coding rules for instruction files is to sample the codebase for consistent patterns, providing evidence-backed suggestions complete with sample counts and file paths for verifiable rule generation.

Related Skills

Explore More Software Engineering Skills→
aRustyDevaRustyDev
1

template-new-skill

Create a new Claude Code Skill directory with SKILL.md, justfile, and meta.json.

Community
Intermediate
eriknovakeriknovak

refactor

Refactor source files to enforce CLAUDE.md coding conventions.

Community
Advanced
musujmusuj

phase-8-review

Review codebases for architecture consistency, convention compliance, and design gaps.

Community
Advanced
otahontasotahontas
1

context-hunter

Identify architectural patterns, naming conventions, and data flow across modules.

Community
Basic