refactoring

[abmmhasan]

Summary

Refactoring to move out commands

Change

Type

• Bug fix
• New feature
• Refactor
• Performance
• Security or reliability
• Documentation or examples
• Dependency, CI or tooling
• Other

Behavior and Compatibility

• No observable behavior changed
• Existing behavior was corrected
• New behavior was introduced
• Public API or documented behavior changed
• Backward compatibility may be affected
• PHP, extension, platform or dependency requirements changed

Validation

Complete Suite

• composer ic:ci

Focused validation

• composer ic:test:syntax
• composer ic:test:code
• composer ic:test:lint
• composer ic:test:sniff
• composer ic:test:duplicates
• composer ic:test:probe
• composer ic:test:comments
• composer ic:test:architecture
• composer ic:test:static
• composer ic:test:security
• composer ic:test:refactor

Coverage

• Expected or newly introduced behavior
• Regression scenario
• Boundary and edge cases
• Failure and exception paths
• Public API compatibility
• Version, dependency, extension or platform-specific behavior
• Not applicable

Performance

• Relevant benchmarks were added or updated
• Results were compared against a relevant baseline

Benchmark commands

• composer ic:benchmark
• composer ic:bench:quick
• composer ic:bench:chart

Implementation Notes

Review Focus

Checklist

• The change is focused and excludes unrelated modifications.
• Tests cover new, corrected and regression-prone behavior.
• Public API and backward-compatibility implications were considered.
• Documentation, examples and type information were updated where required.
• Performance claims are supported by reproducible benchmarks.
• No credentials, secrets, personal data or sensitive debug output are included.
• I followed CONTRIBUTING.md.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.