ginee-rediscover

Re-run ginee project discovery to refresh local artefacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-rediscover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ginee-rediscover
Source: https://github.com/kostiantyn-matsebora/ginee/tree/main/core/skills/ginee-rediscover
Command: npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-rediscover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates re-discovery of a project using the ginee framework to refresh discovery outputs while preserving adopter-authored content. It re-detects everything and overwrites local artefacts; preserves local/roles/ (project-authored).

Core Features & Use Cases

  • Re-run the full Discovery flow to refresh local/project-profile.md, local/bindings.md, local/framework.config.yaml, and local/index/manifest.yaml.
  • Overwrite discovery outputs while preserving adopter-authored local content, enabling a clean reset after major structure changes.
  • Use case: after a repo rewrite or new top-level components, re-run discovery to sync indexes and doc classes.

Quick Start

Run the full 10-step Discovery flow to refresh local discovery artefacts.

Frequently Asked Questions about ginee-rediscover

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

FAQPage Schema
How do I refresh project discovery artifacts after major structure changes?

Re-run the full discovery flow to refresh project artifacts after major structure changes, overwriting local outputs like project-profile.md, bindings.md, framework.config.yaml, and manifest.yaml while preserving adopter-authored content in local/roles/.

What happens to adopter-authored local content when re-running project discovery?

When re-running project discovery, adopter-authored local content in the local/roles/ directory is preserved, while generated discovery outputs such as local/project-profile.md and local/index/manifest.yaml are overwritten with fresh detection results.

When should I re-run full project discovery using the ginee framework?

You should re-run full project discovery when major project structure changes occur, such as a repository rewrite or adding new top-level components, ensuring indexes and documentation classes stay synchronized with the current codebase.

How do I sync indexes and doc classes after a repository rewrite?

To sync indexes and doc classes after a repository rewrite, execute the 10-step discovery flow to re-detect everything and overwrite local artifacts, applying a clean reset that reflects the updated project structure.

Can I overwrite local discovery outputs without losing project-authored roles?

Yes, you can overwrite local discovery outputs without losing project-authored roles because the rediscovery process specifically preserves the local/roles/ directory while replacing generated files like bindings.md and framework.config.yaml.