graft-shared-asset-reuse

Name: graft-shared-asset-reuse
Availability: InStock
Author: gewuyou

Check the Graft asset registry for reuse before modifying shared assets.

6|Updated May 11, 2026

Search Tags:#version control #code management #pre-commit check #asset registry #asset reuse

Ready to run

npx skills add https://github.com/GeWuYou/Graft --skill graft-shared-asset-reuse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: graft-shared-asset-reuse
Source: https://github.com/GeWuYou/Graft/tree/main/.agents/skills/graft-shared-asset-reuse
Command: npx skills add https://github.com/GeWuYou/Graft --skill graft-shared-asset-reuse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage the reuse of Graft's shared assets, ensuring consistency and reducing duplication.

Core Features & Use Cases

Asset Registry Management: Before making changes to assets, this Skill checks the existing registry for reuse opportunities.
Asset Classification: Classify assets as shared, module-owned, contract-owned, or not reusable.
Registry Entry Verification: Ensures new shared assets meet criteria for registry inclusion.
Use Case: Before modifying a reusable component, run this Skill to ensure the changes do not conflict with existing shared assets.

Quick Start

Before making changes to a reusable asset, use 'graft-shared-asset-reuse preflight' to check the asset registry.

Frequently Asked Questions about graft-shared-asset-reuse

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

FAQPage Schema

How do I run a preflight check before modifying shared frontend assets?▼

Run a preflight check to scan the existing asset registry before modifying shared frontend assets, identifying reuse opportunities and preventing conflicts or duplication across modules.

What is asset registry management for code reuse?▼

Asset registry management maintains a curated list of shared, module-owned, and contract-owned assets, requiring manual classification and validation to ensure new assets meet registry inclusion criteria.

How do I classify shared assets as reusable or module-owned?▼

Classify shared assets by manually validating each component against registry criteria, categorizing them as shared, module-owned, contract-owned, or not reusable to maintain boundaries and prevent unauthorized modifications.

Can I use pre-commit checks to prevent duplicate cross-boundary assets?▼

Yes, preflight checks function as pre-commit validations for cross-boundary assets, scanning the registry before asset addition, movement, renaming, removal, or replacement to prevent conflicts with existing shared components.

What are the limitations of automated asset reuse validation?▼

Automated asset reuse validation does not handle classification automatically; the system requires manual classification and validation to determine if an asset is shared, contract-owned, or not reusable before registry entry verification proceeds.