existing-repo

Analyze existing repositories to detect structure, technology stack, and conventions.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill existing-repo-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: existing-repo
Source: https://github.com/lciacci/tessera/tree/main/skills/existing-repo
Command: npx skills add https://github.com/lciacci/tessera --skill existing-repo-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand an unfamiliar repository before making changes, reducing the risk of breaking conventions, missing existing safeguards, or introducing unnecessary tooling.

Core Features & Use Cases

  • Repository Analysis: Detect the project structure, technology stack, entry points, configurations, and documentation.
  • Guardrails Audit and Setup: Evaluate testing, linting, type checking, hooks, commit validation, and security scanning, then recommend or add only missing protections.
  • Convention Preservation: Identify existing naming, formatting, import, testing, and error-handling patterns so new work fits the codebase.
  • Use Case: When joining an unfamiliar application, use this Skill to produce a repository analysis report and establish appropriate safeguards without reorganizing or overwriting existing configuration.

Quick Start

Ask the existing-repo skill to analyze the current repository, document its conventions and guardrails, and recommend the safest next improvements.

Frequently Asked Questions about existing-repo

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

FAQPage Schema
How do I analyze an unfamiliar codebase before making changes?

To analyze an unfamiliar codebase, inspect repository metadata to detect the project structure, technology stack, and entry points. This process identifies existing patterns and configurations, producing a repository analysis report that ensures modifications preserve established conventions safely.

What is the best way to audit existing pre-commit hooks and repository guardrails?

Auditing repository guardrails involves evaluating existing testing, linting, type checking, and pre-commit hooks. This assessment identifies missing development safeguards, allowing you to recommend or add only necessary protections without overwriting established configuration files.

How do I detect codebase conventions without breaking existing patterns?

Detecting codebase conventions requires identifying existing naming, formatting, import, testing, and error-handling patterns. This inspection ensures new code fits the current architecture, preserving established patterns and avoiding unnecessary tooling dependencies or configuration overwrites.

Can I set up development safeguards incrementally on an existing repository?

Yes, you can set up development safeguards incrementally by auditing existing security scanning and commit validation. This approach adds missing protections carefully, avoiding unnecessary dependencies and preventing overwrites to established repository configuration.

When should I avoid reorganizing an unfamiliar repository structure?

You should avoid reorganizing an unfamiliar repository structure when joining a new application, instead prioritizing convention discovery and guardrail audits. This prevents breaking established patterns and missing existing safeguards before modifying code or configuration.