npx claudepluginhub hellblazer/nexus --plugin nx# Codebase Analysis Request
!{
echo "## Context"
echo ""
echo "**Working directory:** $(pwd)"
echo ""
# Project type detection
if [ -f "pom.xml" ]; then
echo "**Project type:** Maven"
echo ''
elif [ -f "build.gradle" ] || [ -f "build.gradle.kts" ]; then
echo "**Project type:** Gradle"
echo ''
elif [ -f "package.json" ]; then
echo "**Project type:** Node.js"
echo ''
else
echo "**Project type:** Unknown"
fi
echo ""
# Module structure
echo "### Top-level Structure"
echo ''
echo ""
# Source locations
echo "### Source Locations"
...Share bugs, ideas, or general feedback.
!{ echo "## Context" echo "" echo "Working directory: $(pwd)" echo ""
if [ -f "pom.xml" ]; then
echo "Project type: Maven"
echo '' grep -E "<artifactId>|<groupId>" pom.xml 2>/dev/null | head -4 || echo "Could not parse pom.xml" echo ''
elif [ -f "build.gradle" ] || [ -f "build.gradle.kts" ]; then
echo "Project type: Gradle"
echo '' head -10 build.gradle* 2>/dev/null || echo "Could not read build.gradle" echo ''
elif [ -f "package.json" ]; then
echo "Project type: Node.js"
echo '' grep -E '"name"|"version"' package.json 2>/dev/null | head -2 || echo "Could not parse package.json" echo ''
else
echo "Project type: Unknown"
fi
echo ""
echo "### Top-level Structure"
echo '' ls -d */ 2>/dev/null | head -15 || echo "No subdirectories" echo ''
echo ""
echo "### Source Locations"
echo '' find . -type d -name "src" 2>/dev/null | grep -v node_modules | grep -v target | head -10 || echo "No src directories found" echo ''
}
Gather project context using MCP tools:
$ARGUMENTS
Invoke the codebase-analysis skill with the following relay. Fill in dynamic fields from the context above:
## Relay: codebase-deep-analyzer
**Task**: Analyze codebase architecture, patterns, and dependencies
**Bead**: [fill from active bead above or 'none']
### Input Artifacts
- Files: [fill from key entry points in project structure above]
### Analysis Scope
$ARGUMENTS
### Deliverable
Comprehensive architecture analysis: module structure map, identified design patterns, dependency graph, entry points, coding conventions, and technical debt assessment.
### Quality Criteria
- [ ] Module structure mapped with responsibilities
- [ ] Key design patterns identified and documented
- [ ] Dependencies documented (internal and external)
- [ ] Entry points identified for each module
- [ ] Coding conventions and idioms noted
For full relay structure and optional fields, see RELAY_TEMPLATE.md.