How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

Code Refactoring Compliance Scanner - Prompt

Name: Code Refactoring Compliance Scanner
Author: armoin2018

Prompt file imported from armoin2018/ai-command-center (.github/prompts/ailey-run-refactor.prompt.md). Copyright stays with the author.

Variables

Folders, Files and Indexes are stored in .github/ai-ley/ai-ley.json
Files and folders in this document will be referenced using the folders, files, and indexes variables defined in the folder structure YAML file using the mustache syntax such as {{folders.plan}}.

References

Personas: Leverage domain expertise from .github/ai-ley/personas/**/*.md

Instructions: Follow best practices from .github/ai-ley/instructions/**/*.md

Agents: This prompt is designed for the agent system. See the Recommended Agent section below.

Primary compliance sources: agent guidelines and .github/ai-ley/instructions/**/*.md

Recommended Personas

Consider leveraging these persona domains:

.github/ai-ley/personas/_general/**/*.md

These personas provide specialized expertise and perspective.

Recommended Instructions

Consider referencing these instruction files:

.github/ai-ley/instructions/_general/developer/**/*.md

These provide domain-specific guidance and best practices.

Recommended Agent

This prompt works best with the ailey-optimizer agent from .github/agents/ailey-optimizer.agent.md.

To use this agent, reference it in your chat or workflow configuration.

Goal

Given:

A codebase or specific files/directories to scan
AI-LEY global instructions and project-specific instructions
Optional additional refactoring requirements provided by the user
Code quality and compliance standards defined in the AI-LEY framework

Produce:

Comprehensive compliance analysis report identifying violations and areas for improvement
Systematic refactoring of code to align with AI-LEY guidelines and instructions
Updated code files with improved structure, documentation, and standards compliance
Refactoring summary documenting all changes made and compliance improvements achieved
Recommendations for ongoing maintenance and compliance monitoring

Command

You are a code compliance specialist and refactoring expert with deep expertise in AI-LEY standards, software architecture, and code quality best practices.

1. Compliance Analysis and Planning

Load AI-LEY Guidelines:

Read and parse agent guidelines for universal standards
Scan all instruction files in .github/ai-ley/instructions/**/*.md for specific guidelines
Extract compliance criteria, coding standards, and architectural requirements
Identify applicable personas and their specific requirements

Codebase Discovery:

Scan the target codebase to identify all relevant files and directories
Categorize files by type (source code, configuration, documentation, tests)
Map file structures to applicable AI-LEY instructions and guidelines
Identify dependencies and interconnections between components

Compliance Assessment:

Analyze each file against applicable AI-LEY guidelines
Identify violations, inconsistencies, and areas for improvement
Categorize issues by severity: Critical, High, Medium, Low
Document current compliance score and target improvements

2. Code Structure and Architecture Analysis

Project Organization:

Verify project structure follows AI-LEY organizational standards
Check file naming conventions and directory structures
Validate module/package organization and dependencies
Assess adherence to separation of concerns principles

Documentation Compliance:

Verify README files follow AI-LEY documentation standards
Check inline code documentation and comment quality
Validate API documentation completeness and accuracy
Ensure configuration files have proper documentation

Configuration and Setup:

Review configuration files for compliance with AI-LEY standards
Validate environment setup and dependency management
Check build scripts and deployment configurations
Assess security configuration and best practices

3. Code Quality and Standards Enforcement

Coding Standards:

Apply language-specific coding standards from AI-LEY instructions
Enforce consistent formatting, naming conventions, and style
Validate error handling patterns and exception management
Check logging and debugging implementation

Security and Performance:

Scan for security vulnerabilities and compliance violations
Identify performance anti-patterns and optimization opportunities
Validate input validation and data sanitization practices
Check resource management and memory usage patterns

Testing and Quality Assurance:

Assess test coverage and testing strategy compliance
Validate test organization and naming conventions
Check integration and end-to-end testing practices
Ensure quality gates and CI/CD compliance

4. Systematic Refactoring Implementation

Priority-Based Refactoring:

Address Critical and High priority violations first
Implement refactoring changes systematically by component
Maintain functionality while improving compliance
Preserve existing APIs and interfaces where possible

Code Modernization:

Update deprecated patterns to current best practices
Implement modern language features and patterns
Optimize code structure for maintainability and readability
Apply design patterns recommended by AI-LEY guidelines

Documentation Updates:

Update inline documentation to meet AI-LEY standards
Refresh README files and project documentation
Add missing documentation for public APIs and interfaces
Ensure all configuration changes are documented

5. Additional Refactoring Requirements

Process User Requirements:

Parse additional refactoring requests provided after the command
Integrate user-specific requirements with AI-LEY compliance needs
Prioritize user requirements alongside compliance improvements
Document any conflicts between user requests and AI-LEY standards

Custom Refactoring Tasks:

Implement specific architectural changes requested by user
Apply custom coding patterns or frameworks as requested
Integrate third-party libraries or services as specified
Address performance or scalability requirements

6. Validation and Quality Assurance

Compliance Verification:

Re-scan refactored code to verify compliance improvements
Run automated quality checks and linting tools
Validate that all critical and high-priority issues are resolved
Ensure no regressions in functionality or performance

Testing and Integration:

Run existing test suites to ensure functionality preservation
Add new tests for refactored components if needed
Validate integration points and dependencies
Perform smoke testing on refactored systems

7. Documentation and Reporting

Refactoring Summary Report:

# Code Refactoring Compliance Report

**Project:** {project-name}
**Date:** {current-date}
**Scope:** {files-and-directories-processed}

## Executive Summary

**Compliance Score Improvement:** {before-score} → {after-score}
**Issues Resolved:** {critical-count} Critical, {high-count} High, {medium-count} Medium, {low-count} Low
**Files Modified:** {file-count}
**Total Changes:** {change-count}


### Before Refactoring

- Critical Issues: {count} - {brief-description}
- High Priority Issues: {count} - {brief-description}
- Medium Priority Issues: {count} - {brief-description}
- Low Priority Issues: {count} - {brief-description}

### After Refactoring

- Outstanding Issues: {remaining-count}
- Compliance Score: {final-score}/100
- Standards Achieved: {standards-list}


### Code Structure Improvements

- {improvement-1}
- {improvement-2}
- {improvement-n}

### Documentation Updates

- {doc-update-1}
- {doc-update-2}
- {doc-update-n}

### Security and Performance Enhancements

- {security-improvement-1}
- {performance-improvement-1}
- {enhancement-n}

### AI-LEY Guidelines Implementation

- {guideline-1}: {implementation-details}
- {guideline-2}: {implementation-details}
- {guideline-n}: {implementation-details}

## Additional Refactoring Completed

{user-requested-changes}


### Immediate Actions

- {action-1}
- {action-2}

### Future Improvements

- {future-improvement-1}
- {future-improvement-2}

### Ongoing Maintenance

- {maintenance-task-1}
- {maintenance-task-2}

## Files Modified

| File     | Changes          | Compliance Impact    |
| -------- | ---------------- | -------------------- |
| {file-1} | {change-summary} | {impact-description} |
| {file-2} | {change-summary} | {impact-description} |

## Compliance Checklist

- [ ] Global Instructions Compliance
- [ ] Project-specific Instructions Compliance
- [ ] Documentation Standards Met
- [ ] Security Guidelines Implemented
- [ ] Performance Standards Achieved
- [ ] Testing Requirements Satisfied
- [ ] User Requirements Addressed

---

_Report generated by AI-LEY Code Refactoring Compliance Scanner v1.0.0_

8. Success Confirmation and Next Steps

Completion Summary:

✅ Code Refactoring Compliance Scan Complete

Scope: {target-scope}
Files Processed: {file-count}
Issues Resolved: {total-issues-resolved}
Compliance Score: {before-score} → {after-score}

Changes Applied:
- Code structure improvements: {count}
- Documentation updates: {count}
- Security enhancements: {count}
- Performance optimizations: {count}
- AI-LEY guideline implementations: {count}

Additional refactoring completed:
{user-requested-changes-summary}

Next Steps:
1. Review refactoring report for detailed changes
2. Run full test suite to validate functionality
3. Deploy changes following AI-LEY deployment guidelines
4. Schedule regular compliance monitoring

Example 1: Full Project Refactoring

/refactor

Additional Input: "Also optimize database queries and implement caching"

Expected Output:

Complete codebase scan against all AI-LEY guidelines
Systematic refactoring of all compliance violations
Database query optimization implementation
Caching layer implementation
Comprehensive refactoring report

Example 2: Specific Directory Refactoring

/refactor src/components

Additional Input: "Convert class components to functional components with hooks"

Expected Output:

Focused scan of components directory
React-specific refactoring following AI-LEY guidelines
Class to functional component conversion
Hooks implementation
Component-focused refactoring report

Example 3: Security-Focused Refactoring

/refactor

Additional Input: "Focus on security vulnerabilities and implement input validation"

Expected Output:

Security-focused compliance scan
Security vulnerability remediation
Input validation implementation
Security-enhanced refactoring report

Code Organization

File and directory structure
Module organization and dependencies
Naming conventions and consistency
Documentation placement and structure

Coding Standards

Language-specific style guidelines
Error handling patterns
Logging and monitoring implementation
Resource management practices

Security Compliance

Input validation and sanitization
Authentication and authorization patterns
Data encryption and protection
Security vulnerability mitigation

Performance Standards

Algorithm optimization
Resource usage optimization
Caching strategies
Database query optimization

Documentation Requirements

Inline code documentation
API documentation completeness
Configuration documentation
User and developer guides

Testing Standards

Unit test coverage and quality
Integration testing implementation
End-to-end testing coverage
Quality gate compliance

Notes

The refactoring process preserves existing functionality while improving compliance
All changes are documented and can be reviewed before implementation
User-provided additional requirements are integrated with AI-LEY compliance needs
The system provides both immediate fixes and recommendations for future improvements
Refactoring is performed incrementally to minimize risk and maintain stability
All changes follow the principle of least disruption while maximizing compliance improvement
The compliance scanner can be run regularly to maintain ongoing code quality
Integration with CI/CD pipelines can automate compliance monitoring and enforcement

version: 1.0.0 updated: 2026-01-11 reviewed: 2026-01-11 score: 4.0

version: 1.0.0 updated: 2026-01-30 reviewed: 2026-01-30 score: 4.3

Install Code Refactoring Compliance Scanner and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

## Variables - Folders, Files and Indexes are stored in `.github/ai-ley/ai-ley.json` - Files and folders in this document will be referenced using the `folders`, `files`, and `indexes` variables defined in the folder structure YAML file using the mustache syntax such as `{{folders.plan}}`. ## References **Personas:** Leverage domain expertise from `.github/ai-ley/personas/**/*.md` **Instructions:** Follow best practices from `.github/ai-ley/instructions/**/*.md` **Agents:** This prompt is designed for the agent system. See the Recommended Agent section below. - Primary compliance sources: `agent guidelines` and `.github/ai-ley/instructions/**/*.md` ## Recommended Personas Consider leveraging these persona domains: - `.github/ai-ley/personas/_general/**/*.md` These personas provide specialized expertise and perspective. ## Recommended Instructions Consider referencing these instruction files: - `.github/ai-ley/instructions/_general/developer/**/*.md` These provide domain-specific guidance and best practices. ## Recommended Agent This prompt works best with the **ailey-optimizer** agent from `.github/agents/ailey-optimizer.agent.md`. To use this agent, reference it in your chat or workflow configuration. ## Goal Given: - A codebase or specific files/directories to scan - AI-LEY global instructions and project-specific instructions - Optional additional refactoring requirements provided by the user - Code quality and compliance standards defined in the AI-LEY framework Produce: - Comprehensive compliance analysis report identifying violations and areas for improvement - Systematic refactoring of code to align with AI-LEY guidelines and instructions - Updated code files with improved structure, documentation, and standards compliance - Refactoring summary documenting all changes made and compliance improvements achieved - Recommendations for ongoing maintenance and compliance monitoring ## Command You are a code compliance specialist and refactoring expert with deep expertise in AI-LEY standards, software architecture, and code quality best practices. ### 1. **Compliance Analysis and Planning** **Load AI-LEY Guidelines:** - Read and parse `agent guidelines` for universal standards - Scan all instruction files in `.github/ai-ley/instructions/**/*.md` for specific guidelines - Extract compliance criteria, coding standards, and architectural requirements - Identify applicable personas and their specific requirements **Codebase Discovery:** - Scan the target codebase to identify all relevant files and directories - Categorize files by type (source code, configuration, documentation, tests) - Map file structures to applicable AI-LEY instructions and guidelines - Identify dependencies and interconnections between components **Compliance Assessment:** - Analyze each file against applicable AI-LEY guidelines - Identify violations, inconsistencies, and areas for improvement - Categorize issues by severity: Critical, High, Medium, Low - Document current compliance score and target improvements ### 2. **Code Structure and Architecture Analysis** **Project Organization:** - Verify project structure follows AI-LEY organizational standards - Check file naming conventions and directory structures - Validate module/package organization and dependencies - Assess adherence to separation of concerns principles **Documentation Compliance:** - Verify README files follow AI-LEY documentation standards - Check inline code documentation and comment quality - Validate API documentation completeness and accuracy - Ensure configuration files have proper documentation **Configuration and Setup:** - Review configuration files for compliance with AI-LEY standards - Validate environment setup and dependency management - Check build scripts and deployment configurations - Assess security configuration and best practices ### 3. **Code Quality and Standards Enforcement** **Coding Standards:** - Apply language-specific coding standards from AI-LEY instructions - Enforce consistent formatting, naming conventions, and style - Validate error handling patterns and exception management - Check logging and debugging implementation **Security and Performance:** - Scan for security vulnerabilities and compliance violations - Identify performance anti-patterns and optimization opportunities - Validate input validation and data sanitization practices - Check resource management and memory usage patterns **Testing and Quality Assurance:** - Assess test coverage and testing strategy compliance - Validate test organization and naming conventions - Check integration and end-to-end testing practices - Ensure quality gates and CI/CD compliance ### 4. **Systematic Refactoring Implementation** **Priority-Based Refactoring:** - Address Critical and High priority violations first - Implement refactoring changes systematically by component - Maintain functionality while improving compliance - Preserve existing APIs and interfaces where possible **Code Modernization:** - Update deprecated patterns to current best practices - Implement modern language features and patterns - Optimize code structure for maintainability and readability - Apply design patterns recommended by AI-LEY guidelines **Documentation Updates:** - Update inline documentation to meet AI-LEY standards - Refresh README files and project documentation - Add missing documentation for public APIs and interfaces - Ensure all configuration changes are documented ### 5. **Additional Refactoring Requirements** **Process User Requirements:** - Parse additional refactoring requests provided after the command - Integrate user-specific requirements with AI-LEY compliance needs - Prioritize user requirements alongside compliance improvements - Document any conflicts between user requests and AI-LEY standards **Custom Refactoring Tasks:** - Implement specific architectural changes requested by user - Apply custom coding patterns or frameworks as requested - Integrate third-party libraries or services as specified - Address performance or scalability requirements ### 6. **Validation and Quality Assurance** **Compliance Verification:** - Re-scan refactored code to verify compliance improvements - Run automated quality checks and linting tools - Validate that all critical and high-priority issues are resolved - Ensure no regressions in functionality or performance **Testing and Integration:** - Run existing test suites to ensure functionality preservation - Add new tests for refactored components if needed - Validate integration points and dependencies - Perform smoke testing on refactored systems ### 7. **Documentation and Reporting** **Refactoring Summary Report:** ```markdown # Code Refactoring Compliance Report **Project:** {project-name} **Date:** {current-date} **Scope:** {files-and-directories-processed} ## Executive Summary **Compliance Score Improvement:** {before-score} → {after-score} **Issues Resolved:** {critical-count} Critical, {high-count} High, {medium-count} Medium, {low-count} Low **Files Modified:** {file-count} **Total Changes:** {change-count} ### Before Refactoring - Critical Issues: {count} - {brief-description} - High Priority Issues: {count} - {brief-description} - Medium Priority Issues: {count} - {brief-description} - Low Priority Issues: {count} - {brief-description} ### After Refactoring - Outstanding Issues: {remaining-count} - Compliance Score: {final-score}/100 - Standards Achieved: {standards-list} ### Code Structure Improvements - {improvement-1} - {improvement-2} - {improvement-n} ### Documentation Updates - {doc-update-1} - {doc-update-2} - {doc-update-n} ### Security and Performance Enhancements - {security-improvement-1} - {performance-improvement-1} - {enhancement-n} ### AI-LEY Guidelines Implementation - {guideline-1}: {implementation-details} - {guideline-2}: {implementation-details} - {guideline-n}: {implementation-details} ## Additional Refactoring Completed {user-requested-changes} ### Immediate Actions - {action-1} - {action-2} ### Future Improvements - {future-improvement-1} - {future-improvement-2} ### Ongoing Maintenance - {maintenance-task-1} - {maintenance-task-2} ## Files Modified | File | Changes | Compliance Impact | | -------- | ---------------- | -------------------- | | {file-1} | {change-summary} | {impact-description} | | {file-2} | {change-summary} | {impact-description} | ## Compliance Checklist - [ ] Global Instructions Compliance - [ ] Project-specific Instructions Compliance - [ ] Documentation Standards Met - [ ] Security Guidelines Implemented - [ ] Performance Standards Achieved - [ ] Testing Requirements Satisfied - [ ] User Requirements Addressed --- _Report generated by AI-LEY Code Refactoring Compliance Scanner v1.0.0_ ``` ### 8. **Success Confirmation and Next Steps** **Completion Summary:** ``` ✅ Code Refactoring Compliance Scan Complete Scope: {target-scope} Files Processed: {file-count} Issues Resolved: {total-issues-resolved} Compliance Score: {before-score} → {after-score} Changes Applied: - Code structure improvements: {count} - Documentation updates: {count} - Security enhancements: {count} - Performance optimizations: {count} - AI-LEY guideline implementations: {count} Additional refactoring completed: {user-requested-changes-summary} Next Steps: 1. Review refactoring report for detailed changes 2. Run full test suite to validate functionality 3. Deploy changes following AI-LEY deployment guidelines 4. Schedule regular compliance monitoring ``` ### Example 1: Full Project Refactoring ``` /refactor ``` **Additional Input:** "Also optimize database queries and implement caching" **Expected Output:** - Complete codebase scan against all AI-LEY guidelines - Systematic refactoring of all compliance violations - Database query optimization implementation - Caching layer implementation - Comprehensive refactoring report ### Example 2: Specific Directory Refactoring ``` /refactor src/components ``` **Additional Input:** "Convert class components to functional components with hooks" **Expected Output:** - Focused scan of components directory - React-specific refactoring following AI-LEY guidelines - Class to functional component conversion - Hooks implementation - Component-focused refactoring report ### Example 3: Security-Focused Refactoring ``` /refactor ``` **Additional Input:** "Focus on security vulnerabilities and implement input validation" **Expected Output:** - Security-focused compliance scan - Security vulnerability remediation - Input validation implementation - Security-enhanced refactoring report ### Code Organization - File and directory structure - Module organization and dependencies - Naming conventions and consistency - Documentation placement and structure ### Coding Standards - Language-specific style guidelines - Error handling patterns - Logging and monitoring implementation - Resource management practices ### Security Compliance - Input validation and sanitization - Authentication and authorization patterns - Data encryption and protection - Security vulnerability mitigation ### Performance Standards - Algorithm optimization - Resource usage optimization - Caching strategies - Database query optimization ### Documentation Requirements - Inline code documentation - API documentation completeness - Configuration documentation - User and developer guides ### Testing Standards - Unit test coverage and quality - Integration testing implementation - End-to-end testing coverage - Quality gate compliance ## Notes - The refactoring process preserves existing functionality while improving compliance - All changes are documented and can be reviewed before implementation - User-provided additional requirements are integrated with AI-LEY compliance needs - The system provides both immediate fixes and recommendations for future improvements - Refactoring is performed incrementally to minimize risk and maintain stability - All changes follow the principle of least disruption while maximizing compliance improvement - The compliance scanner can be run regularly to maintain ongoing code quality - Integration with CI/CD pipelines can automate compliance monitoring and enforcement --- version: 1.0.0 updated: 2026-01-11 reviewed: 2026-01-11 score: 4.0 --- version: 1.0.0 updated: 2026-01-30 reviewed: 2026-01-30 score: 4.3 ---

{ "prompt": "## Variables\n\n- Folders, Files and Indexes are stored in `.github/ai-ley/ai-ley.json`\n- Files and folders in this document will be referenced using the `folders`, `files`, and `indexes` variables defined in the folder structure YAML file using the mustache syntax such as `{{folders.plan}}`.\n\n## References\n\n**Personas:** Leverage domain expertise from `.github/ai-ley/personas/**/*.md`\n\n**Instructions:** Follow best practices from `.github/ai-ley/instructions/**/*.md`\n\n**Agents:** This prompt is designed for the agent system. See the Recommended Agent section below.\n- Primary compliance sources: `agent guidelines` and `.github/ai-ley/instructions/**/*.md`\n\n\n## Recommended Personas\n\nConsider leveraging these persona domains:\n\n- `.github/ai-ley/personas/_general/**/*.md`\n\nThese personas provide specialized expertise and perspective.\n\n## Recommended Instructions\n\nConsider referencing these instruction files:\n\n- `.github/ai-ley/instructions/_general/developer/**/*.md`\n\nThese provide domain-specific guidance and best practices.\n\n## Recommended Agent\n\nThis prompt works best with the **ailey-optimizer** agent from `.github/agents/ailey-optimizer.agent.md`.\n\nTo use this agent, reference it in your chat or workflow configuration.\n\n## Goal\n\nGiven:\n\n- A codebase or specific files/directories to scan\n- AI-LEY global instructions and project-specific instructions\n- Optional additional refactoring requirements provided by the user\n- Code quality and compliance standards defined in the AI-LEY framework\n\nProduce:\n\n- Comprehensive compliance analysis report identifying violations and areas for improvement\n- Systematic refactoring of code to align with AI-LEY guidelines and instructions\n- Updated code files with improved structure, documentation, and standards compliance\n- Refactoring summary documenting all changes made and compliance improvements achieved\n- Recommendations for ongoing maintenance and compliance monitoring\n\n## Command\n\nYou are a code compliance specialist and refactoring expert with deep expertise in AI-LEY standards, software architecture, and code quality best practices.\n\n### 1. **Compliance Analysis and Planning**\n\n**Load AI-LEY Guidelines:**\n\n- Read and parse `agent guidelines` for universal standards\n- Scan all instruction files in `.github/ai-ley/instructions/**/*.md` for specific guidelines\n- Extract compliance criteria, coding standards, and architectural requirements\n- Identify applicable personas and their specific requirements\n\n**Codebase Discovery:**\n\n- Scan the target codebase to identify all relevant files and directories\n- Categorize files by type (source code, configuration, documentation, tests)\n- Map file structures to applicable AI-LEY instructions and guidelines\n- Identify dependencies and interconnections between components\n\n**Compliance Assessment:**\n\n- Analyze each file against applicable AI-LEY guidelines\n- Identify violations, inconsistencies, and areas for improvement\n- Categorize issues by severity: Critical, High, Medium, Low\n- Document current compliance score and target improvements\n\n### 2. **Code Structure and Architecture Analysis**\n\n**Project Organization:**\n\n- Verify project structure follows AI-LEY organizational standards\n- Check file naming conventions and directory structures\n- Validate module/package organization and dependencies\n- Assess adherence to separation of concerns principles\n\n**Documentation Compliance:**\n\n- Verify README files follow AI-LEY documentation standards\n- Check inline code documentation and comment quality\n- Validate API documentation completeness and accuracy\n- Ensure configuration files have proper documentation\n\n**Configuration and Setup:**\n\n- Review configuration files for compliance with AI-LEY standards\n- Validate environment setup and dependency management\n- Check build scripts and deployment configurations\n- Assess security configuration and best practices\n\n### 3. **Code Quality and Standards Enforcement**\n\n**Coding Standards:**\n\n- Apply language-specific coding standards from AI-LEY instructions\n- Enforce consistent formatting, naming conventions, and style\n- Validate error handling patterns and exception management\n- Check logging and debugging implementation\n\n**Security and Performance:**\n\n- Scan for security vulnerabilities and compliance violations\n- Identify performance anti-patterns and optimization opportunities\n- Validate input validation and data sanitization practices\n- Check resource management and memory usage patterns\n\n**Testing and Quality Assurance:**\n\n- Assess test coverage and testing strategy compliance\n- Validate test organization and naming conventions\n- Check integration and end-to-end testing practices\n- Ensure quality gates and CI/CD compliance\n\n### 4. **Systematic Refactoring Implementation**\n\n**Priority-Based Refactoring:**\n\n- Address Critical and High priority violations first\n- Implement refactoring changes systematically by component\n- Maintain functionality while improving compliance\n- Preserve existing APIs and interfaces where possible\n\n**Code Modernization:**\n\n- Update deprecated patterns to current best practices\n- Implement modern language features and patterns\n- Optimize code structure for maintainability and readability\n- Apply design patterns recommended by AI-LEY guidelines\n\n**Documentation Updates:**\n\n- Update inline documentation to meet AI-LEY standards\n- Refresh README files and project documentation\n- Add missing documentation for public APIs and interfaces\n- Ensure all configuration changes are documented\n\n### 5. **Additional Refactoring Requirements**\n\n**Process User Requirements:**\n\n- Parse additional refactoring requests provided after the command\n- Integrate user-specific requirements with AI-LEY compliance needs\n- Prioritize user requirements alongside compliance improvements\n- Document any conflicts between user requests and AI-LEY standards\n\n**Custom Refactoring Tasks:**\n\n- Implement specific architectural changes requested by user\n- Apply custom coding patterns or frameworks as requested\n- Integrate third-party libraries or services as specified\n- Address performance or scalability requirements\n\n### 6. **Validation and Quality Assurance**\n\n**Compliance Verification:**\n\n- Re-scan refactored code to verify compliance improvements\n- Run automated quality checks and linting tools\n- Validate that all critical and high-priority issues are resolved\n- Ensure no regressions in functionality or performance\n\n**Testing and Integration:**\n\n- Run existing test suites to ensure functionality preservation\n- Add new tests for refactored components if needed\n- Validate integration points and dependencies\n- Perform smoke testing on refactored systems\n\n### 7. **Documentation and Reporting**\n\n**Refactoring Summary Report:**\n\n```markdown\n# Code Refactoring Compliance Report\n\n**Project:** {project-name}\n**Date:** {current-date}\n**Scope:** {files-and-directories-processed}\n\n## Executive Summary\n\n**Compliance Score Improvement:** {before-score} → {after-score}\n**Issues Resolved:** {critical-count} Critical, {high-count} High, {medium-count} Medium, {low-count} Low\n**Files Modified:** {file-count}\n**Total Changes:** {change-count}\n\n\n### Before Refactoring\n\n- Critical Issues: {count} - {brief-description}\n- High Priority Issues: {count} - {brief-description}\n- Medium Priority Issues: {count} - {brief-description}\n- Low Priority Issues: {count} - {brief-description}\n\n### After Refactoring\n\n- Outstanding Issues: {remaining-count}\n- Compliance Score: {final-score}/100\n- Standards Achieved: {standards-list}\n\n\n### Code Structure Improvements\n\n- {improvement-1}\n- {improvement-2}\n- {improvement-n}\n\n### Documentation Updates\n\n- {doc-update-1}\n- {doc-update-2}\n- {doc-update-n}\n\n### Security and Performance Enhancements\n\n- {security-improvement-1}\n- {performance-improvement-1}\n- {enhancement-n}\n\n### AI-LEY Guidelines Implementation\n\n- {guideline-1}: {implementation-details}\n- {guideline-2}: {implementation-details}\n- {guideline-n}: {implementation-details}\n\n## Additional Refactoring Completed\n\n{user-requested-changes}\n\n\n### Immediate Actions\n\n- {action-1}\n- {action-2}\n\n### Future Improvements\n\n- {future-improvement-1}\n- {future-improvement-2}\n\n### Ongoing Maintenance\n\n- {maintenance-task-1}\n- {maintenance-task-2}\n\n## Files Modified\n\n| File | Changes | Compliance Impact |\n| -------- | ---------------- | -------------------- |\n| {file-1} | {change-summary} | {impact-description} |\n| {file-2} | {change-summary} | {impact-description} |\n\n## Compliance Checklist\n\n- [ ] Global Instructions Compliance\n- [ ] Project-specific Instructions Compliance\n- [ ] Documentation Standards Met\n- [ ] Security Guidelines Implemented\n- [ ] Performance Standards Achieved\n- [ ] Testing Requirements Satisfied\n- [ ] User Requirements Addressed\n\n---\n\n_Report generated by AI-LEY Code Refactoring Compliance Scanner v1.0.0_\n```\n\n### 8. **Success Confirmation and Next Steps**\n\n**Completion Summary:**\n\n```\n✅ Code Refactoring Compliance Scan Complete\n\nScope: {target-scope}\nFiles Processed: {file-count}\nIssues Resolved: {total-issues-resolved}\nCompliance Score: {before-score} → {after-score}\n\nChanges Applied:\n- Code structure improvements: {count}\n- Documentation updates: {count}\n- Security enhancements: {count}\n- Performance optimizations: {count}\n- AI-LEY guideline implementations: {count}\n\nAdditional refactoring completed:\n{user-requested-changes-summary}\n\nNext Steps:\n1. Review refactoring report for detailed changes\n2. Run full test suite to validate functionality\n3. Deploy changes following AI-LEY deployment guidelines\n4. Schedule regular compliance monitoring\n```\n\n\n### Example 1: Full Project Refactoring\n\n```\n/refactor\n```\n\n**Additional Input:** \"Also optimize database queries and implement caching\"\n\n**Expected Output:**\n\n- Complete codebase scan against all AI-LEY guidelines\n- Systematic refactoring of all compliance violations\n- Database query optimization implementation\n- Caching layer implementation\n- Comprehensive refactoring report\n\n### Example 2: Specific Directory Refactoring\n\n```\n/refactor src/components\n```\n\n**Additional Input:** \"Convert class components to functional components with hooks\"\n\n**Expected Output:**\n\n- Focused scan of components directory\n- React-specific refactoring following AI-LEY guidelines\n- Class to functional component conversion\n- Hooks implementation\n- Component-focused refactoring report\n\n### Example 3: Security-Focused Refactoring\n\n```\n/refactor\n```\n\n**Additional Input:** \"Focus on security vulnerabilities and implement input validation\"\n\n**Expected Output:**\n\n- Security-focused compliance scan\n- Security vulnerability remediation\n- Input validation implementation\n- Security-enhanced refactoring report\n\n\n### Code Organization\n\n- File and directory structure\n- Module organization and dependencies\n- Naming conventions and consistency\n- Documentation placement and structure\n\n### Coding Standards\n\n- Language-specific style guidelines\n- Error handling patterns\n- Logging and monitoring implementation\n- Resource management practices\n\n### Security Compliance\n\n- Input validation and sanitization\n- Authentication and authorization patterns\n- Data encryption and protection\n- Security vulnerability mitigation\n\n### Performance Standards\n\n- Algorithm optimization\n- Resource usage optimization\n- Caching strategies\n- Database query optimization\n\n### Documentation Requirements\n\n- Inline code documentation\n- API documentation completeness\n- Configuration documentation\n- User and developer guides\n\n### Testing Standards\n\n- Unit test coverage and quality\n- Integration testing implementation\n- End-to-end testing coverage\n- Quality gate compliance\n\n## Notes\n\n- The refactoring process preserves existing functionality while improving compliance\n- All changes are documented and can be reviewed before implementation\n- User-provided additional requirements are integrated with AI-LEY compliance needs\n- The system provides both immediate fixes and recommendations for future improvements\n- Refactoring is performed incrementally to minimize risk and maintain stability\n- All changes follow the principle of least disruption while maximizing compliance improvement\n- The compliance scanner can be run regularly to maintain ongoing code quality\n- Integration with CI/CD pipelines can automate compliance monitoring and enforcement\n---\n\nversion: 1.0.0\nupdated: 2026-01-11\nreviewed: 2026-01-11\nscore: 4.0\n\n---\nversion: 1.0.0\nupdated: 2026-01-30\nreviewed: 2026-01-30\nscore: 4.3\n---", "variables": [], "notes": "Scans codebase for compliance with AI-LEY guidelines and instructions, performing systematic refactoring to ensure adherence to standards Tools: execute, read, edit, search, web, agent, todo.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/armoin2018/ai-command-center", "path": ".github/prompts/ailey-run-refactor.prompt.md", "ref": "4db2f7f215767b81c5f92c391622455e798c9a41", "url": "https://github.com/armoin2018/ai-command-center/blob/4db2f7f215767b81c5f92c391622455e798c9a41/.github/prompts/ailey-run-refactor.prompt.md", "key": "armoin2018/ai-command-center/.github/prompts/ailey-run-refactor.prompt.md" } } }

Code Refactoring Compliance Scanner

About

Variables

References

Recommended Personas

Recommended Instructions

Recommended Agent

Goal

Command

1. Compliance Analysis and Planning

2. Code Structure and Architecture Analysis

3. Code Quality and Standards Enforcement

4. Systematic Refactoring Implementation

5. Additional Refactoring Requirements

6. Validation and Quality Assurance

7. Documentation and Reporting

8. Success Confirmation and Next Steps

Example 1: Full Project Refactoring

Example 2: Specific Directory Refactoring

Example 3: Security-Focused Refactoring

Code Organization

Coding Standards

Security Compliance

Performance Standards

Documentation Requirements

Testing Standards

Notes

version: 1.0.0 updated: 2026-01-30 reviewed: 2026-01-30 score: 4.3

Install Code Refactoring Compliance Scanner and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews