skills.rest
kostiantyn-matsebora
kostiantyn-matseboraCOMMUNITY
Explore all skills by this author →
GitHub

ginee-discovery

Detect project stack and SDLC tooling, then write local profile files.

Updated Aug 27, 2026
Search Tags:#automation#discovery#project-setup#config-generation#stack-detection#ginee
One-click install
npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ginee-discovery
Source: https://github.com/kostiantyn-matsebora/ginee/tree/main/core/skills/ginee-discovery
Command: npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial discovery phase for a ginee deployment, ensuring a project is quickly profiled and ready for setup.

Core Features & Use Cases

  • Detects project stack, domain, architecture artefacts, and SDLC tooling.
  • Writes local/profile files (local/project-profile.md, local/bindings.md, local/framework.config.yaml) and dispatches population tasks.
  • Use Case: On starting a new framework install, run discovery to generate the project profile and configuration.

Quick Start

Run the ginee initial discovery to generate local/project-profile.md, local/bindings.md, and local/framework.config.yaml for the project.

Frequently Asked Questions about ginee-discovery

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

FAQPage Schema
How do I automate project stack detection and config generation for a new framework install?▼

Project stack detection works by scanning local project metadata to identify frameworks, artefacts, and SDLC tooling, then generating local configuration files like project-profile.md and framework.config.yaml to bootstrap the deployment.

What files are generated during initial project discovery?▼

Initial project discovery generates local/project-profile.md, local/bindings.md, and local/framework.config.yaml, while dispatching tasks to populate local/index/manifest.yaml with detected artefact and tooling data.

When do I need to run project discovery on an existing codebase?▼

You need to run project discovery when starting a new framework install or when local project metadata is missing, ensuring the codebase is profiled and configured for deployment.

How does stack detection identify architecture artefacts and SDLC tooling?▼

Stack detection identifies architecture artefacts and SDLC tooling by analyzing the project directory structure and configuration, writing the detected stack and domain data into local profile files and a manifest.

Do I need any dependencies to generate a project profile and bindings?▼

Generating a project profile and bindings requires no external dependencies, as the discovery process runs autonomously to detect the stack, write local configuration files, and dispatch population tasks.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
brazil-benchbrazil-bench
11

re-evaluate

Detect new commits and closed issues, then re-run evaluations and update reports.

Official
Advanced
tomzxtomzx
5

initialize-sdlc-directory

Create missing .sdlc/ directories and copy default templates without overwriting existing files.

Community
Intermediate
toilahuonggtoilahuongg
10

readme

Update README.md with documentation from codebase analysis.

Community
Basic