project-context

Maintain project file-tree and code-structure snapshots in a SQLite cache.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/YuluoY/nimis --skill project-context-yuluoy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-context
Source: https://github.com/YuluoY/nimis/tree/main/skills-en/project-context
Command: npx skills add https://github.com/YuluoY/nimis --skill project-context-yuluoy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

AI coding agents frequently lose awareness of a project's file tree and exported symbols across sessions, forcing repeated rescans and causing missed context; project-context solves this by maintaining a persistent, queryable snapshot of the project's structure and code summaries in a local SQLite cache.

Core Features & Use Cases

  • Incremental init and sync that records file metadata (path, mtime, hash, category) into .cache/context.db without modifying source files.
  • Query and validate capabilities to list module files, exported symbols, detect stale entries, and mark deleted files; dependency extraction for inter-file import graphs.
  • Knowledge insertion for Deliver-stage extraction (knowledge_edges and knowledge_flows) and a phase guard integration for Plan→Execute→Validate→Deliver workflows.
  • Use cases include orchestrator-driven context sensing before route selection, focused module inspection, project-wide dependency analysis, and restoring project awareness across agent sessions.

Quick Start

Run the init action to create a project snapshot and persist structure data to .cache/context.db.

Frequently Asked Questions about project-context

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

FAQPage Schema
How do I persist project file-tree and code structure across AI agent sessions?

To persist project structure across sessions, run an incremental sync that records file metadata, mtime, and hash into a local SQLite cache (.cache/context.db), preventing AI agents from losing project context without modifying source files.

How does incremental dependency scanning work for codebases?

Incremental dependency scanning works by using mtime and hash checks to sync file changes, extracting inter-file import graphs and code summaries to detect stale entries and record deleted files in a local SQLite database.

How do I extract and insert knowledge from code modules for AI workflows?

To extract knowledge from code modules, use CLI operations to insert knowledge_edges and knowledge_flows during the Deliver stage, integrating a phase guard for Plan, Execute, Validate, and Deliver agent workflows.

Can I query exported symbols and module files without a full rescan?

Yes, you can query exported symbols and module files directly from the persistent SQLite context database, using validate and query CLI operations to list metadata and inspect focused modules without triggering a full project rescan.

Does this project context tracking approach modify my source code files?

No, this project context tracking approach does not modify source code files; it performs read-only incremental syncs of file metadata, categories, and dependency graphs, storing all extracted context exclusively in the .cache/context.db database.

When should I run a stale-check for project context synchronization?

You should run a stale-check when AI agents need accurate project awareness, using the CLI to detect stale database entries, mark deleted files, and validate that inter-file dependencies and code summaries match the current file-tree state.