verify-config

النجوم٠

التفرعات١

آخر تحديث١٧ مارس ٢٠٢٦ في ١٩:٣٥

Audits CLAUDE.md and .claude/ reference files against actual codebase patterns. Use to detect configuration drift and ensure documentation stays in sync with the codebase.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

I-Synergy

I-Synergy/I-Synergy.NugetPackageManager

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	verify-config
description	Audits CLAUDE.md and .claude/ reference files against actual codebase patterns. Use to detect configuration drift and ensure documentation stays in sync with the codebase.

Verify Configuration Skill

Audits project documentation against actual codebase conventions to detect and fix drift.

Steps

Read current documentation
- Read CLAUDE.md
- Read .claude/reference/critical-rules.md
- Read .claude/patterns/cqrs-patterns.md
- Extract all documented conventions (data access patterns, naming, file structure, mapping, etc.)
Sample the codebase for actual patterns
- Pick ISynergy.Domain.Budgets as the reference implementation
- Read 2-3 command handlers (Create, Update, Delete)
- Read 2-3 query handlers (GetById, GetList)
- Read the Mappers/Configuration.cs
- Read 2-3 Model records from Models/
- Read 2-3 Response records
- Check Extensions/ServiceCollectionExtensions.cs
Compare and report
- For each documented convention, verify it matches the actual code
- Check for patterns in the code that are NOT documented
- Categorize findings:
  - Correct — documentation matches code
  - Drift — documentation contradicts code
  - Missing — code pattern not documented
  - Stale — documented pattern no longer used
Check .claude/ folder structure
- Verify .claude/settings.json has plansDirectory pointing to local .claude/plans
- Verify .claude/progress/ and .claude/plans/ folders exist
- Check that no project-specific config leaked to global ~/.claude/
Present findings
- Show a summary table of all conventions checked with their status
- For each Drift/Missing/Stale finding, show the documented vs actual pattern
- Propose specific edits to fix any drift found
- Wait for user approval before making changes

Output Format

## Configuration Audit Report

### Summary
- Conventions checked: N
- Correct: N
- Drift detected: N
- Missing documentation: N
- Stale documentation: N

### Findings

| # | Convention | Status | Details |
|---|-----------|--------|---------|
| 1 | Data access style | Correct/Drift/Missing/Stale | ... |
| 2 | ... | ... | ... |

### Recommended Fixes
1. ...
2. ...

المزيد من هذا المستودع

نفس المستودع

api-security

I-Synergy/I-Synergy.NugetPackageManager

API security specialist. Use for securing APIs, implementing authentication/authorization, protecting against OWASP API Top 10, or handling security best practices.

2026-03-170

architect

I-Synergy/I-Synergy.NugetPackageManager

Solution architecture and system design expert. Use when designing system architecture, choosing technology stacks, making architectural decisions, or defining bounded contexts.

2026-03-170

blazor-specialist

I-Synergy/I-Synergy.NugetPackageManager

Blazor UI development specialist. Use for building Blazor Server or WebAssembly apps, component development, state management, or form handling.

2026-03-170

code-reviewer

I-Synergy/I-Synergy.NugetPackageManager

Code quality and architecture review specialist. Use when reviewing code for SOLID principles, CQRS patterns, security issues, or architecture compliance before merging.

2026-03-170

database-migration

I-Synergy/I-Synergy.NugetPackageManager

EF Core migrations and database specialist. Use when creating/applying database migrations, designing schemas, optimizing queries, or managing PostgreSQL databases.

2026-03-170

devops-engineer

I-Synergy/I-Synergy.NugetPackageManager

DevOps and CI/CD specialist. Use for building pipelines, containerization, infrastructure as code, or deployment automation. User-invocable only for production deployments.

2026-03-170

Verify Configuration Skill

Audits project documentation against actual codebase conventions to detect and fix drift.

Steps

Read current documentation

Read CLAUDE.md
Read .claude/reference/critical-rules.md
Read .claude/patterns/cqrs-patterns.md
Extract all documented conventions (data access patterns, naming, file structure, mapping, etc.)

Sample the codebase for actual patterns

Pick ISynergy.Domain.Budgets as the reference implementation
Read 2-3 command handlers (Create, Update, Delete)
Read 2-3 query handlers (GetById, GetList)
Read the Mappers/Configuration.cs
Read 2-3 Model records from Models/
Read 2-3 Response records
Check Extensions/ServiceCollectionExtensions.cs

Compare and report

For each documented convention, verify it matches the actual code
Check for patterns in the code that are NOT documented
Categorize findings:
- Correct — documentation matches code
- Drift — documentation contradicts code
- Missing — code pattern not documented
- Stale — documented pattern no longer used

Check .claude/ folder structure

Verify .claude/settings.json has plansDirectory pointing to local .claude/plans
Verify .claude/progress/ and .claude/plans/ folders exist
Check that no project-specific config leaked to global ~/.claude/

Present findings

Show a summary table of all conventions checked with their status
For each Drift/Missing/Stale finding, show the documented vs actual pattern
Propose specific edits to fix any drift found
Wait for user approval before making changes

Output Format

## Configuration Audit Report ### Summary - Conventions checked: N - Correct: N - Drift detected: N - Missing documentation: N - Stale documentation: N ### Findings | # | Convention | Status | Details | |---|-----------|--------|---------| | 1 | Data access style | Correct/Drift/Missing/Stale | ... | | 2 | ... | ... | ... | ### Recommended Fixes 1. ... 2. ...