repo-analyser

Analyzes software repositories and generates a .planning/CONVENTIONS.md file detailing findings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jamesbondev/ai-dotfiles --skill repo-analyser-jamesbondev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-analyser
Source: https://github.com/jamesbondev/ai-dotfiles/tree/main/.github/skills/repo-analyser
Command: npx skills add https://github.com/jamesbondev/ai-dotfiles --skill repo-analyser-jamesbondev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps understand the conventions, architecture, and patterns within a software repository, ensuring consistency and adherence to existing practices.

Core Features & Use Cases

  • Convention Discovery: Analyzes code structure, dependencies, testing approaches, and coding styles.
  • Pattern Identification: Detects common architectural patterns like Vertical Slice, Clean Architecture, etc.
  • Use Case: Before starting work on a new project, use this Skill to quickly grasp how the codebase is organized and how to contribute effectively.

Quick Start

Use the repo-analyser skill to discover the conventions of the current repository.

Frequently Asked Questions about repo-analyser

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

FAQPage Schema
How do I discover coding conventions and architecture patterns in an unfamiliar repository?

To discover coding conventions in an unfamiliar repository, analyze the codebase structure, dependencies, and testing strategies to identify established architectural patterns and generate a conventions document for new contributors.

What is the best way to understand a codebase before contributing as a new developer?

Understanding a codebase before contributing involves analyzing the repository's coding styles, architectural patterns, and testing approaches to ensure new code adheres to existing practices and maintains consistency.

How do I identify architectural patterns like Clean Architecture or Vertical Slice in a project?

Identifying architectural patterns like Clean Architecture or Vertical Slice requires analyzing the repository's code structure and module organization to detect common conventions and document the findings.

Can I document repository conventions and coding standards for my team automatically?

You can automatically document repository conventions by analyzing the code structure, dependencies, and testing strategies to generate a `.planning/CONVENTIONS.md` file detailing the project's established practices.

Does this repository analysis approach require any specific dependencies or setup?

Repository analysis for convention discovery requires no specific dependencies or setup tools, functioning directly on the software repository to extract coding styles and architectural patterns.

When should I analyze repository conventions instead of reading the code manually?

Analyzing repository conventions is preferable when conventions are unclear or when onboarding new contributors, as it systematically identifies architectural patterns and testing strategies faster than manual code review.