Loading...
Loading...
Found 14 Skills
Comprehensive code review for diffs. Analyzes changed code for security vulnerabilities, anti-patterns, and quality issues. Auto-detects domain (frontend/backend) from file paths.
Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.
General Architecture Governance Specification, providing layering constraints, impact analysis, interface contracts, and dependency injection baselines. Suitable for architecture review, refactoring, and new module design of any multi-layer system.
Trace downstream data lineage and impact analysis. Use when the user asks what depends on this data, what breaks if something changes, downstream dependencies, or needs to assess change risk before modifying a table or DAG.
Semantic code search, relationship mapping, and codebase intelligence. Provides deep code analysis including symbol search, dependency tracking, change impact analysis, and codebase Q&A.
Local-first code intelligence — structural search, symbol context, impact analysis, and dead code detection via typed graph traversal. Use this skill when you need to search a codebase by intent (not just substring), understand how symbols connect, trace change impact before refactoring, find dead code, or get an architecture briefing. Triggers on: search codebase, find symbol, who calls, blast radius, impact analysis, dead code, code graph, structural search, architecture overview, codebase orientation, understand connections, what depends on, find where.
Use codanna MCP tools for semantic code search, call graphs, and impact analysis before grep/find.
Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-omniscript), building FlexCards (use sf-flexcard), creating Integration Procedures (use sf-integration-procedure), or configuring Data Mappers (use sf-datamapper).
Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-industry-commoncore-omniscript), building FlexCards (use sf-industry-commoncore-flexcard), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or configuring Data Mappers (use sf-industry-commoncore-datamapper).
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
Agent-powered GitHub PR reviews with smart semantic triage. Categorizes changes as MECHANICAL (skip), NEW LOGIC (read), or BEHAVIORAL (verify) — so agents never waste tokens reading lock files or formatting diffs. Includes remote file reading, text/AST search across PR or full repo, and comment posting. No local clone needed. Use when asked to review a PR, check a pull request, look at PR changes, or given a PR number/URL to review.
This skill should be used when the user asks to "create CI", "CMDB", "configuration item", "CI relationship", "impact analysis", "dependency map", "cmdb_ci", "asset", or any ServiceNow CMDB and configuration management development.