codebaseanalyser

DevOps Community

Skill notes

When to Use This Skill

Use this skill when: Deployed application functionality is not working correctly in production Need comprehensive deep analysis of entire codebase Authentication system issues in production Deployment pipeline debugging is required

Phase 1: Perform Full Codebase Architecture Analysis

Analyze the complete project structure Identify: Frontend framework and architecture Backend framework and architecture Database type and connection method

Phase 2: Execute Authentication System Deep Trace

Identify: Login route Registration route Token generation logic Token validation middleware

Phase 3: Execute File-Level and Line-Level Connection Audit

Check every import/export Verify that: All API routes match frontend calls All controllers are properly connected All middleware is applied

Phase 4: Execute Deployment & Production Debugging

Analyze: Build process Environment variables in hosting platform Backend server configuration Reverse proxy (if any)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@SARAMALI15792 · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Perform Full Codebase Architecture Analysis

Analyze the complete project structure Identify: Frontend framework and architecture Backend framework and architecture Database type and connection method

02
Phase 2: Execute Authentication System Deep Trace

Identify: Login route Registration route Token generation logic Token validation middleware

03
Phase 3: Execute File-Level and Line-Level Connection Audit

Check every import/export Verify that: All API routes match frontend calls All controllers are properly connected All middleware is applied

04
Phase 4: Execute Deployment & Production Debugging

Analyze: Build process Environment variables in hosting platform Backend server configuration Reverse proxy (if any)

05
Phase 5: Implement CI/CD Pipeline Setup for Auto-Testing

Implement a CI/CD solution that: Automatically runs tests on: Every push Every pull request Tests:

06
Phase 6: Create Stability Improvement Plan

Create: Refactoring suggestions Security improvements Logging improvements Monitoring suggestions

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.