codebaseanalyser
- Repo stars 5
- License MIT
- Author updated Live
- Author repo AINativeBook
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Env read
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: codebaseanalyser
description: Performs comprehensive deep analysis of entire codebase and deployment pipeline to identify issu…
category: devops
runtime: no special runtime
---
# codebaseanalyser output preview
## PART A: Task fit
- Use case: Performs comprehensive deep analysis of entire codebase and deployment pipeline to identify issues in production environment. Conducts systematic investigation across architecture, authentication, file connections, deployment, CI/CD, and stability..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use This Skill / How to Execute the Skill / Phase 1: Perform Full Codebase Architecture Analysis” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Performs comprehensive deep analysis of entire codebase and deployment pipeline to identify issues in production environment. Conducts systematic investigation across architecture, authentication, file connections, deployment, CI/CD, and stability.”.
- **02** When the source has headings, the agent prioritizes “When to Use This Skill / How to Execute the Skill / Phase 1: Perform Full Codebase Architecture Analysis” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands, read environment variables.
Validate with a small run
Start with a small task and check whether the result follows “When to Use This Skill / How to Execute the Skill / Phase 1: Perform Full Codebase Architecture Analysis”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: codebaseanalyser
description: Performs comprehensive deep analysis of entire codebase and deployment pipeline to identify issu…
category: devops
source: SARAMALI15792/AINativeBook
---
# codebaseanalyser
## When to use
- Performs comprehensive deep analysis of entire codebase and deployment pipeline to identify issues in production envir…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use This Skill / How to Execute the Skill / Phase 1: Perform Full Codebase Architecture Analysis” and keep inference separate from source facts.
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "codebaseanalyser" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use This Skill / How to Execute the Skill / Phase 1: Perform Full Codebase Architecture Analysis
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands, read environment variables | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Codebase Analyser
Perform comprehensive deep analysis of entire codebase and deployment pipeline to identify why functionality is not working correctly in production. Execute systematic investigation across all aspects of the application including architecture, authentication, file-level connections, deployment, CI/CD pipeline, and stability improvements.
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
- CI/CD setup for auto-testing is needed
- Stability improvements and refactoring suggestions are required
- File-level and line-level connection audits are needed
How to Execute the Skill
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
- Authentication system implementation
- API communication pattern
- Environment configuration (.env usage)
- Deployment configuration
- Create a clear architecture map showing:
- How frontend communicates with backend
- How backend communicates with database
- How authentication flows through the system
Phase 2: Execute Authentication System Deep Trace
- Identify:
- Login route
- Registration route
- Token generation logic
- Token validation middleware
- Session or JWT handling
- Password hashing method
- Cookie handling (if any)
- Trace authentication flow step-by-step:
- User submits login form (frontend)
- Request sent to backend
- Backend processes credentials
- Token created
- Token returned to frontend
- Token stored (localStorage/cookies)
- Protected routes accessed
- Check for:
- CORS issues
- Missing credentials in fetch/axios
- Wrong base URLs
- Environment variable misconfiguration
- Production vs development differences
- Missing middleware
- Expired tokens
- Wrong secret keys
- API route mismatches
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
- Database models are properly registered
- No circular dependencies exist
- Identify any dead code or unused functions
- Detect any runtime-only production errors
Provide a categorized issue list:
- Critical
- Major
- Minor
Phase 4: Execute Deployment & Production Debugging
Analyze:
- Build process
- Environment variables in hosting platform
- Backend server configuration
- Reverse proxy (if any)
- Port binding
- Production logs
- CORS production policy
- HTTPS issues
Explain why it might work locally but fail after deployment.
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:
- API endpoints
- Authentication flow
- Database connection
- Environment variable validation
- Frontend build success
- Fails deployment if tests fail
- Runs linting and type-checking
- Verifies that backend can start successfully
- Verifies that frontend can build without errors
Provide:
- Suggested GitHub Actions (or CI provider) config
- Example workflow YAML file
- Suggested test structure
- Suggested test libraries
Phase 6: Create Stability Improvement Plan
Create:
- Refactoring suggestions
- Security improvements
- Logging improvements
- Monitoring suggestions
- Error handling improvements
- Recommended production-grade best practices
Resources Available
- Run
scripts/codebase_analysis.pyfor automated codebase analysis - Reference
references/production_debugging.mdfor common production issues and debugging patterns - Use
assets/github-workflow.ymlas a template for CI/CD workflow
Important Guidelines
- Do not give generic advice
- Analyze the actual code deeply
- Explain root causes clearly
- Provide fixes with code examples
- Be systematic and structured
- Focus on production-specific issues
- Prioritize critical issues that prevent functionality
- Identify environment-specific configurations
- Ensure comprehensive coverage of all system components
Decide Fit First
Design Intent
How To Use It
Boundaries And Review