director:refresh

Re-scan codebase files and update project context summaries.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/noahrasheta/director --skill director-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: director:refresh
Source: https://github.com/noahrasheta/director/tree/main/skills/refresh
Command: npx skills add https://github.com/noahrasheta/director --skill director-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-scan your codebase and optionally re-run research to keep your project context current.

Core Features & Use Cases

  • Codebase refresh: Re-scan project files to update architecture, conventions, and dependencies.
  • Optional research refresh: When requested, re-run domain research to align context with the latest codebase.
  • Change-aware updates: Generates updated .director/codebase/SUMMARY.md and, if needed, .director/research/SUMMARY.md, and reports meaningful changes.

Quick Start

Run the director:refresh command to re-scan your codebase and optionally refresh research to keep context up to date.

Frequently Asked Questions about director:refresh

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

FAQPage Schema
How do I refresh codebase context after making changes to my project files?

To refresh codebase context, you can re-scan project files to update architecture, conventions, and dependencies, which generates an updated SUMMARY.md reflecting the current state of your codebase.

What is the best way to update project context and research simultaneously?

Updating project context and research simultaneously requires a full scope refresh, triggered by passing arguments like 'research', 'everything', 'all', or 'full' to re-run domain research and re-scan the codebase together.

When do I need to re-scan my codebase to keep project context current?

You need to re-scan your codebase when significant changes occur in project files, ensuring your architecture and dependency context stays aligned with the actual codebase.

Does a codebase refresh save the current state before updating context?

Yes, a codebase refresh saves the current state before running the mapping pipeline and synthesizer, ensuring previous context is preserved while generating updated summary files.

How does updating project context track completed goals?

Updating project context tracks completed goals by writing the current goal count and date into config.json, ensuring your project metadata reflects ongoing progress alongside the refreshed summary.