infer-project-profile-from-code

Infer a project-profile artifact from scan-index.json evidence.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill infer-project-profile-from-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: infer-project-profile-from-code
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/infer-project-profile-from-code
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill infer-project-profile-from-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an existing codebase into a structured project-profile proposal when you cannot run a full product interview, so your downstream product-keeper workflows still start with grounded evidence.

Core Features & Use Cases

  • Evidence-grounded profile inference: Infers product identity, team shape, technology posture, compliance hints, platform targets, and delivery maturity strictly from scan-index.json signals.
  • Brownfield bootstrap for /codify: Supports the /codify phase by reverse-engineering the foundational project-profile.yaml that is normally collected via user interview.
  • Confidence-aware output: Marks missing or truncated scan signals as null with low confidence, and records explicit decision entries in a decision manifest for transparency.

Quick Start

Call infer-project-profile-from-code during /codify with scan-index.json and issue context to generate user-provided/project-profile.yaml under the STM evidence path.

Frequently Asked Questions about infer-project-profile-from-code

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

FAQPage Schema
How do I bootstrap a product profile from an existing codebase?▼

Bootstrap a product profile from an existing codebase by scanning manifests, git contributors, CI signals, and documentation to infer a foundational project profile artifact without conducting a user interview.

What is evidence-grounded project profile inference?▼

Evidence-grounded project profile inference is deriving product identity, technology posture, and delivery maturity strictly from validated scan-index.json signals, tagging confidence levels to prevent fabrication when data is missing.

Can I generate a project profile for brownfield repositories without a user interview?▼

Yes, you can generate a project profile for brownfield repositories without a user interview by reverse-engineering scan evidence like manifests and CI test signals into a structured project-profile.yaml artifact.

How do I infer compliance hints and delivery maturity from code scans?▼

Infer compliance hints and delivery maturity from code scans by processing captured git contributor data, CI test type-check signals, and documentation hints through field-by-field inference with cited scan evidence paths.

What happens when scan signals are missing during codebase profile inference?▼

When scan signals are missing or truncated during codebase profile inference, the system marks fields as null with low confidence and records explicit decision entries in a manifest to ensure output transparency.

Does brownfield bootstrap require specific inputs for codebase profile generation?▼

Brownfield bootstrap requires validated scan-index.json inputs capturing manifests, git contributors, CI test type-check signals, and documentation hints, along with issue context to generate the foundational profile.