bootspring_analyze

Analyze code, projects, and context to understand structure and provide intelligent suggestions.

Overview#

The bootspring_analyze tool provides deep analysis of your project's codebase, context, and current state. It powers intelligent suggestions by understanding patterns, detecting the development phase, and recommending appropriate agents and workflows.

Parameters#

ParameterTypeRequiredDescription
contextstringNoContext text or code to analyze
scopestringNoAnalysis scope: file, directory, project
optionsobjectNoAnalysis options

Options Object#

OptionTypeDefaultDescription
includePatternsbooleantrueDetect code patterns
includeStackbooleantrueDetect tech stack
includePhasebooleantrueDetect development phase
deepbooleanfalsePerform deep analysis

Usage Examples#

Analyze Context#

Use the bootspring_analyze tool with: - context: "Building a user authentication system with OAuth"

Response:

Loading code block...

Project Analysis#

Use the bootspring_analyze tool with: - scope: "project" - options: { deep: true }

Response:

Loading code block...

File Analysis#

Use the bootspring_analyze tool with: - context: "[file contents here]" - scope: "file"

Analysis Capabilities#

Phase Detection#

The tool detects the current development phase:

PhaseDescription
initializationProject setup and scaffolding
feature-developmentBuilding new features
testingWriting and running tests
debuggingFixing issues
optimizationPerformance improvements
deploymentPreparing for production
maintenanceOngoing updates

Pattern Detection#

Identifies code patterns and conventions:

  • Component patterns (functional, class-based)
  • State management approach
  • API design patterns
  • Error handling patterns
  • Testing patterns

Stack Detection#

Detects technologies in use:

  • Framework (Next.js, React, Vue, etc.)
  • Language (TypeScript, JavaScript)
  • Styling (Tailwind, CSS Modules, styled-components)
  • Database (PostgreSQL, MySQL, MongoDB)
  • ORM (Prisma, Drizzle, TypeORM)
  • Testing (Vitest, Jest, Playwright)

Response Format#

Success Response#

Loading code block...

Error Response#

Loading code block...

Tier Availability#

FeatureFreeProTeam
Basic analysis
Phase detection
Pattern detectionLimited
Deep analysis-
Custom patterns--

Best Practices#

Provide Context#

Include relevant context for better analysis:

  • Current task description
  • Error messages if debugging
  • File contents for code analysis

Use Appropriate Scope#

  • file - For single file analysis
  • directory - For module or component analysis
  • project - For overall project health

Follow Suggestions#

Act on the agent and skill suggestions to get the best guidance for your current work.