update-graft-inventory

Synchronize feature flag inventory across migration scripts, JSON, and production D1 database.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill update-graft-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-graft-inventory
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/update-graft-inventory
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill update-graft-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill ensures that the project's feature flag inventory is accurate and up-to-date, preventing discrepancies between code, documentation, and production.

Core Features & Use Cases

  • Automated Inventory Updates: Automatically updates the .github/graft-inventory.json file based on changes in migration scripts and production database states.
  • Discrepancy Detection: Identifies new, removed, or changed feature flags by comparing migration files, the inventory file, and the production database.
  • Use Case: After deploying a new feature flag via a migration script, run this skill to automatically update the central inventory file and the KnownGraftId type definition, ensuring documentation and CI checks remain synchronized.

Quick Start

Run the update-graft-inventory skill to synchronize the feature flag inventory with the latest changes.

Frequently Asked Questions about update-graft-inventory

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

FAQPage Schema
How do I synchronize feature flag inventory with my production database?

To synchronize feature flag inventory, a process compares migration scripts, the inventory JSON file, and the production D1 database to automatically update metadata and type definitions for accurate project documentation.

Why does my CI check fail after adding a new feature flag migration?

CI checks fail when the feature flag inventory has discrepancies between migration scripts, the inventory JSON file, and the production D1 database. Running a synchronization process updates the inventory and type definitions to resolve these mismatches.

What is the best way to update graft type definitions after a database migration?

The best way to update graft type definitions is to compare migration scripts against the production D1 database and the inventory JSON file. This automatically updates the KnownGraftId type definition to reflect the current feature flag status.

Does synchronizing feature flags require manual edits to the inventory JSON file?

Synchronizing feature flags does not require manual edits to the inventory JSON file. The process automatically identifies new, removed, or changed flags by comparing migrations and the production D1 database, then updates the file directly.

Can I detect discrepancies in feature flag counts between code and production?

You can detect discrepancies in feature flag counts by comparing migration files, the inventory JSON file, and the production D1 database. This process identifies new, removed, or changed flags to ensure accurate project documentation.