Skill

refactor-project-context

Use when scanning and reorganizing all project context files (AGENTS.md, README.md, gotchas.md, .claude/rules/) for consistency, accuracy, and structural alignment.

From context

Install

Run in your terminal

npx claudepluginhub masseater/claude-code-plugin --plugin context

Tool Access

This skill is limited to using the following tools:

ReadWrite(.claude/**)Write(AGENTS.md)Write(README.md)Write(**/AGENTS.md)Write(**/README.md)Bash(ls)Bash(mkdir)GlobGrepTodoWriteAskUserQuestionSkill(context:should-be-project-context)Skill(research:semtools)Skill(context:refactor-context-file)Skill(context:verify-context)

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Organize and synchronize all context files across the project.

Execution Steps

0. Load Skill

Load the should-be-project-context Skill to understand the templates and processing rules.

1. Detect Project Structure

Infer the project structure from:

workspaces field in package.json
pnpm-workspace.yaml
Directory layout

Present the detected structure via AskUserQuestion:

Detected project structure:
- Root: /path/to/project
- Sub-packages:
  - packages/xxx
  - packages/yyy

Proceed with this structure?

2. Scan Target Files

Search for the following files/directories:

**/AGENTS.md
**/README.md
.claude/rules/*.md
**/CLAUDE.md: Enforce that these contain only @AGENTS.md. Migrate any other content to AGENTS.md

List all found files and confirm processing order via AskUserQuestion.

3. Verify and Rename CLAUDE.md

Check all CLAUDE.md files. If any contain content beyond the AGENTS.md reference, rename them to AGENTS.md. If AGENTS.md already exists in the same directory, merge using AGENTS.md as the base.

4a. Generate CLAUDE.md

Detect directories where AGENTS.md exists but CLAUDE.md does not, then create CLAUDE.md with:

echo "@AGENTS.md" >> "CLAUDE.md"

This ensures AGENTS.md serves as the SSOT, with CLAUDE.md acting as a reference-only alias.

4b. Process README.md

For each README.md, follow the should-be-project-context Skill criteria:

Extract content that belongs in AGENTS.md
Update the command list (all slash commands; npm scripts with user confirmation)
Unify formatting per template; update context files as needed

5. Process Context Files

For each context file (AGENTS.md, .claude/rules/*.md):

Run /context:verify-context <file-path> to verify technical accuracy
Run /context:refactor-context-file <file-path> for detailed decomposition and refactoring

Running verification first prevents propagating incorrect information during refactoring.

6. Per-File Confirmation Flow

For each file:

Analyze current content
Display change proposals
Confirm with user (approve / modify / skip)
Apply approved changes

7. Completion Report

List of created/updated files
Deleted/archived content
Content remaining in gotchas.md (with reasons if applicable)
Recommended next actions