
Enhance Cross File
- 63 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/agentsys
enhance-cross-file is a Claude skill that analyzes cross-file consistency across agents, skills, and workflows to catch mismatches single-file checks miss.
About
This skill analyzes cross-file semantic consistency across agents, skills, and workflows. It runs a JavaScript analyzer that finds tools used in a prompt body but not declared in frontmatter, references to nonexistent agents, duplicate instructions, and contradictory ALWAYS-versus-NEVER rules. All findings are MEDIUM certainty and require human review rather than auto-fix.
- Detects tools used but not declared, and nonexistent agent references
- Flags duplicate instructions and contradictory ALWAYS/NEVER rules across files
- Eight cross-file patterns, none auto-fixed, to force human review
Enhance Cross File by the numbers
- 63 all-time installs (skills.sh)
- Ranked #6,234 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
enhance-cross-file capabilities & compatibility
- Capabilities
- cross file analysis · agent config review · consistency check
- Use cases
- code review · documentation
What enhance-cross-file says it does
Analyze cross-file semantic consistency across agents, skills, and workflows.
Detects issues that span multiple files - things single-file analysis misses:
npx skills add https://github.com/avifenesh/agentsys --skill enhance-cross-fileAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 63 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/agentsys ↗ |
What it does
Analyze cross-file consistency across agents, skills, and workflows to catch mismatches single-file checks miss.
Who is it for?
Catching inconsistencies that span multiple agent, skill, and workflow files
Skip if: Single-file linting or reviewing application code
When should I use this skill?
The user wants to check cross-file consistency across tools, frontmatter, agent references, and rules
What you get
A grouped report of cross-file inconsistencies for human review across agents, skills, and workflows.
- grouped cross-file findings report
By the numbers
- 8 cross-file patterns
- 0 auto-fixable patterns
Files
enhance-cross-file
Analyze cross-file semantic consistency across agents, skills, and workflows.
Parse Arguments
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const targetPath = args.find(a => !a.startsWith('--')) || '.';Purpose
Detects issues that span multiple files - things single-file analysis misses:
- Tools used in prompt body but not declared in frontmatter
- Agent references that don't exist
- Duplicate instructions across files (maintenance burden)
- Contradictory rules (ALWAYS vs NEVER conflicts)
- Orphaned agents not referenced by any workflow
- Skill tool mismatches (allowed-tools vs actual usage)
Workflow
1. Run Analyzer - Execute the JavaScript analyzer to get findings:
node -e "const a = require('./lib/enhance/cross-file-analyzer.js'); console.log(JSON.stringify(a.analyze('.'), null, 2));"For a specific path: a.analyze('./plugins/enhance')
2. Parse Results - The analyzer returns JSON with summary and findings 3. Report - Return findings grouped by category
The JavaScript analyzer (lib/enhance/cross-file-analyzer.js) implements all cross-file detection. The patterns below are reference documentation.
Detection Patterns
1. Tool Consistency (MEDIUM Certainty)
tool_not_in_allowed_list: Tool used in prompt body but not in frontmatter tools: list
# Frontmatter declares:
tools: Read, Grep
# But body uses:
Use Write({ file_path: "/out" }) # <- Not declared!skill_tool_mismatch: Skill's allowed-tools doesn't match actual tool usage in skill body
2. Workflow Consistency (MEDIUM Certainty)
missing_workflow_agent: subagent_type: "plugin:agent-name" references non-existent agent
orphaned_prompt: Agent file exists but no workflow references it (may be entry point - check manually)
incomplete_phase_transition: Workflow phase mentions "Phase N" but no corresponding section
3. Instruction Consistency (MEDIUM Certainty)
duplicate_instructions: Same MUST/NEVER instruction in 3+ files (extract to shared location)
contradictory_rules: One file says "ALWAYS X" while another says "NEVER X"
Output Format
## Cross-File Analysis
**Files Analyzed**: {agents} agents, {skills} skills, {commands} commands
### Tool Consistency ({n})
| Agent | Issue | Fix |
|-------|-------|-----|
| exploration-agent | Uses Write but not in tools list | Add Write to frontmatter |
### Workflow Issues ({n})
| Source | Issue | Fix |
|--------|-------|-----|
| workflow.md | References nonexistent agent | Check spelling or create agent |
### Instruction Consistency ({n})
| Instruction | Files | Fix |
|-------------|-------|-----|
| "NEVER push --force" | 4 files | Extract to CLAUDE.md |Constraints
- All patterns are MEDIUM certainty (require context)
- No auto-fix (cross-file changes need human review)
- Skip content inside
<bad-example>,<bad_example>,<badexample>tags - Skip content inside code blocks with "bad" in info string
- Entry point agents (orchestrator, validator, discoverer) are not orphaned
Pattern Statistics
| Category | Patterns | Auto-Fixable |
|---|---|---|
| Tool Consistency | 2 | 0 |
| Workflow | 3 | 0 |
| Consistency | 3 | 0 |
| Total | 8 | 0 |
Related skills
FAQ
What does it catch that single-file checks miss?
Undeclared tools, references to nonexistent agents, duplicate instructions, contradictory rules, and orphaned agents.
Does it auto-fix?
No, all patterns are MEDIUM certainty and require human review, so nothing is auto-fixed.