skills.rest
Derek-X-Wang
Derek-X-WangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

repo-knowledge-share

Catalogs cross-project tech stacks and features into Markdown knowledge files.

Updated Mar 21, 2026
Search Tags:#automation#markdown#knowledge-management#scan#knowledge-sharing#cross-repo
One-click install
npx skills add https://github.com/Derek-X-Wang/skills --skill repo-knowledge-share
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-knowledge-share
Source: https://github.com/Derek-X-Wang/skills/tree/main/repo-knowledge-share
Command: npx skills add https://github.com/Derek-X-Wang/skills --skill repo-knowledge-share

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-project knowledge sharing to catalog features and tech stacks across repos so you can reuse implementations. Use when building a feature that another project might already have, when the user asks "has any project done X?", or says "scan this project" / "update knowledge". Also triggers automatically on any invocation if the current project's knowledge is stale (>7 days since last scan).

Core Features & Use Cases

  • Catalogs features and tech stacks across repos to enable rapid reuse and reference.
  • Triggers automatic knowledge scans if current project knowledge is stale, ensuring up-to-date references.
  • Provides per-project knowledge entries at knowledge/<project-slug>.md and a local config with last_scanned timestamps.

Quick Start

Run a knowledge scan of the current project to populate or refresh knowledge entries.

Frequently Asked Questions about repo-knowledge-share

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

FAQPage Schema
How do I catalog cross-project knowledge to find if another repository already implemented a feature?▼

Cross-project knowledge cataloging scans repositories to generate structured Markdown files at knowledge/<slug>.md detailing tech stacks and features, enabling you to query existing implementations across multiple repositories.

What is the best way to automate knowledge sharing across multiple repositories?▼

Automating knowledge sharing across repositories is achieved by scanning projects to write structured Markdown describing features and tech stacks. The system automatically triggers a refresh scan if a project's knowledge entry becomes stale.

How do I scan a project to generate a tech stack and feature summary?▼

Scanning a project to generate a tech stack and feature summary creates a structured Markdown knowledge file at knowledge/<slug>.md. This file contains the project's tech stack details and a last_scanned timestamp for staleness tracking.

When does cross-repo knowledge automatically refresh to ensure references are up to date?▼

Cross-repo knowledge automatically refreshes when the current project's knowledge is stale, specifically if more than 7 days have passed since the last_scanned timestamp. This ensures your feature and tech stack references remain current.

Do I need any external dependencies to maintain cross-repo knowledge files?▼

No external dependencies are required to maintain cross-repo knowledge files. The system writes structured Markdown files locally at knowledge/<slug>.md with a last_scanned timestamp to manage staleness and trigger automatic refreshes.

Related Skills

Explore More Software Engineering Skills→
JuniYadiJuniYadi

codebase-analyzer

Analyze codebases to identify tech stack, architecture, and integration touchpoints.

Community
Intermediate
0xBigBoss0xBigBoss
53

extract-transcripts

Extract Claude Code and Codex session JSONL transcripts into Markdown.

Community
Basic
sukeun1997sukeun1997

arch-diagram

Generate interactive five-perspective architecture diagrams with Mermaid runtime flows and custom HTML/CSS.

Community
Advanced
aaronlordaaronlord
1

update-docs

Audit static context files and update project documentation using git and grep.

Community
Advanced