Cortivex Node Type Reference
Every node in a Cortivex pipeline is an instance of a node type. Each node type defines a specialized agent role with default behaviors, model assignments, and configuration options.
Node Type Summary Table
| # | Node Type | Category | Description | Default Model | Avg Cost | Avg Runtime | |---|-----------|----------|-------------|---------------|----------|-------------| | 1 | SecurityScanner | analysis | Scans code for vulnerabilities, insecure patterns, and dependency risks | claude-sonnet-4-20250514 | $0.004 | 15s | | 2 | CodeReviewer | analysis | Reviews code for quality, patterns, bugs, and best practices | claude-sonnet-4-20250514 | $0.018 | 45s | | 3 | BugHunter | analysis | Actively searches for bugs, edge cases, and logic errors | claude-sonnet-4-20250514 | $0.015 | 40s | | 4 | PerformanceProfiler | analysis | Identifies performance bottlenecks and optimization opportunities | claude-sonnet-4-20250514 | $0.012 | 35s | | 5 | ArchitectAnalyzer | analysis | Analyzes codebase structure, dependencies, and architecture patterns | claude-sonnet-4-20250514 | $0.020 | 50s | | 6 | AutoFixer | modification | Automatically fixes identified issues in code | claude-sonnet-4-20250514 | $0.012 | 30s | | 7 | LintFixer | modification | Runs linters and auto-fixes style/formatting issues | claude-haiku-4-20250414 | $0.002 | 10s | | 8 | RefactorAgent | modification | Performs structural refactoring while preserving behavior | claude-sonnet-4-20250514 | $0.025 | 60s | | 9 | TypeMigrator | modification | Converts JavaScript to TypeScript with type annotations | claude-sonnet-4-20250514 | $0.030 | 90s | | 10 | DependencyUpdater | modification | Updates dependencies, resolves conflicts, applies migrations | claude-sonnet-4-20250514 | $0.008 | 20s | | 11 | TestGenerator | testing | Generates unit tests for untested or under-tested code | claude-sonnet-4-20250514 | $0.022 | 55s | | 12 | E2ETestWriter | testing | Generates end-to-end tests using Playwright, Cypress, or similar | claude-sonnet-4-20250514 | $0.025 | 65s | | 13 | TestRunner | testing | Executes test suites and reports results with coverage | claude-haiku-4-20250414 | $0.003 | 60s | | 14 | DocWriter | documentation | Generates or updates documentation (README, API docs, guides) | claude-sonnet-4-20250514 | $0.015 | 40s | | 15 | ChangelogWriter | documentation | Generates changelogs from git history and code analysis | claude-haiku-4-20250414 | $0.004 | 12s | | 16 | CodeExplainer | documentation | Produces human-readable explanations of code for onboarding | claude-sonnet-4-20250514 | $0.016 | 42s | | 17 | APIDesigner | design | Designs REST/GraphQL API schemas from requirements | claude-sonnet-4-20250514 | $0.018 | 50s | | 18 | PRCreator | integration | Creates or updates pull requests with summaries and labels | claude-haiku-4-20250414 | $0.003 | 8s | | 19 | Orchestrator | control | Meta-node that coordinates sub-pipelines or conditional branches | claude-sonnet-4-20250514 | $0.005 | 5s | | 20 | CustomAgent | custom | User-defined agent with fully custom system prompt and tools | configurable | varies | varies |
Detailed Node Type Reference
1. SecurityScanner
Category: analysis Purpose: Scans source code and dependencies for security vulnerabilities, insecure coding patterns, exposed secrets, and known CVEs in dependencies.
When to use:
- Before merging any PR that touches authentication, authorization, cryptography, or data handling
- As part of nightly or pre-release security audits
- When onboarding a new dependency
- After any code change to security-sensitive modules
Default configuration:
- id: security_scan
type: SecurityScanner
config:
model: claude-sonnet-4-20250514
scan_depth: standard # shallow | standard | deep
check_dependencies: true # scan package.json / requirements.txt / Cargo.toml etc.
check_secrets: true # scan for hardcoded secrets, API keys, tokens
check_patterns: true # scan for insecure coding patterns (SQL injection, XSS, etc.)
severity_threshold: medium # low | medium | high | critical (only report at or above)
ignore_paths: # paths to exclude from scanning
- node_modules/
- vendor/
- "*.test.*"
cve_database: latest # use latest CVE database
max_files: 500 # limit to avoid excessive cost on huge repos
output_format: structured # structured | markdown | sarifOutput:
{
"vulnerabilities": [
{
"severity": "high",
"type": "sql_injection",
"file": "src/db/queries.ts",
"line": 47,
"description": "User input directly interpolated into SQL query",
"recommendation": "Use parameterized queries",
"cwe": "CWE-89"
}
],
"dependency_issues": [
{
"package": "lodash",
"version": "4.17.15",
"cve": "CVE-2021-23337",
"severity": "high",
"fix_version": "4.17.21"
}
],
"secrets_found": 0,
"summary": {
"total_issues": 3,
"critical": 0,
"high": 2,
"medium": 1,
"low": 0
}
}2. CodeReviewer
Category: analysis Purpose: Performs comprehensive code review, checking for code quality, design patterns, potential bugs, naming conventions, complexity, and adherence to best practices.
When to use:
- On every PR before merging
- When reviewing unfamiliar code
- After large refactors to validate quality
- As part of periodic codebase quality audits
Default configuration:
- id: code_review
type: CodeReviewer
config:
model: claude-sonnet-4-20250514
review_scope: changed_files # changed_files | full | directory
target_path: null # specific directory to review (when scope is directory)
check_patterns: # what to check for
- error-handling
- naming-conventions
- complexity
- dry-violations
- dead-code
- type-safety
- edge-cases
- documentation
max_issues: 50 # cap issues to avoid overwhelming output
severity_levels: true # categorize issues by severity
suggest_fixes: true # include fix suggestions for each issue
ignore_patterns: # file patterns to skip
- "*.generated.*"
- "*.min.*"
complexity_threshold: 15 # cyclomatic complexity warning threshold
line_length_limit: 120 # flag lines exceeding this lengthOutput:
{
"issues": [
{
"severity": "warning",
"category": "complexity",
"file": "src/utils/parser.ts",
"line": 23,
"description": "Function parseInput has cyclomatic complexity of 18 (threshold: 15)",
"suggestion": "Extract nested conditionals into helper functions"
}
],
"summary": {
"files_reviewed": 12,
"total_issues": 7,
"errors": 1,
"warnings": 4,
"info": 2
},
"overall_quality": "good"
}3. BugHunter
Category: analysis Purpose: Actively searches for bugs, logic errors, race conditions, off-by-one errors, null pointer issues, and other defects that could cause runtime failures.
When to use:
- When investigating reported bugs to find root cause and related issues
- As part of pre-release quality gates
- On complex business logic code
- After major refactors to catch regressions
Default configuration:
- id: bug_hunt
type: BugHunter
config:
model: claude-sonnet-4-20250514
hunt_scope: changed_files # changed_files | full | directory
target_path: null
bug_categories: # what types of bugs to hunt
- null-safety
- off-by-one
- race-conditions
- resource-leaks
- type-coercion
- boundary-conditions
- error-propagation
- state-mutations
include_edge_cases: true # look for edge case inputs that could trigger bugs
trace_dat