oss-investigative-architecture

Name: oss-investigative-architecture
Availability: InStock
Author: Growthub

Analyze repository runtime topology, contracts, invariants, and extension points.

48|12|Updated Mar 27, 2026

Search Tags:#architecture #repository #contracts #analyze #oss #extension-points #phased-plan

Ready to run

npx skills add https://github.com/Growthub-ai/growthub-local --skill oss-investigative-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-investigative-architecture
Source: https://github.com/Growthub-ai/growthub-local/tree/main/.claude/skills/oss-investigative-architecture
Command: npx skills add https://github.com/Growthub-ai/growthub-local --skill oss-investigative-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

Investigate the real architecture of a repository before proposing changes — map runtime topology, contracts, invariants, and extension points, then produce an additive, phased implementation plan grounded in source files rather than assumptions. Use when the user asks to analyze an OSS repo or SDK, plan an adapter/provider/integration extension, audit a workflow or agentic runtime, review a PR against architecture truth, or draft an implementation module for a monorepo.

Frequently Asked Questions about oss-investigative-architecture

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

FAQPage Schema

How do I analyze an OSS repository architecture before extending it?▼

To analyze an OSS repository architecture, you map its runtime topology, contracts, invariants, and extension points from actual source files. This investigation reveals what already exists versus what is missing, ensuring your proposed extension plan is grounded in reality rather than assumptions.

What is the best way to plan an additive integration for an SDK?▼

The best way to plan an additive SDK integration is to identify existing contracts and extension points, then categorize findings into what already exists, partially exists, or is missing. This approach produces a phased implementation plan that preserves existing contracts while safely extending functionality.

How does a repository contract audit work for monorepo pull requests?▼

A repository contract audit reviews a pull request against the architecture truth by mapping runtime topology and citing exact file paths. It checks whether changes align with existing invariants and contracts, categorizing the impact to ensure modifications do not break established extension points.

Can I use architecture analysis to draft an implementation module for a monorepo?▼

Yes, you can draft an implementation module for a monorepo by first investigating its runtime topology and extension points. The analysis provides an additive, phased plan grounded in specific source files, categorizing existing components and missing elements to guide safe module development.

Does this approach work for auditing agentic runtime workflows?▼

Yes, this approach applies to auditing agentic runtime workflows by mapping their topology and identifying invariants. It categorizes findings into existing, partially existing, missing, or proposed elements, ensuring any workflow extensions preserve the runtime's established contracts and safe operation.

When do I need to map extension points instead of just reading the source code?▼

You need to map extension points when planning an adapter, provider, or integration extension for a repository. Mapping runtime topology and contracts ensures your changes are additive and contract-aligned, preventing architectural violations that occur when relying solely on reading source code.