* Logging utility

Safely parse a mathematical expression string.

* Create finding from risk definition

Format the result in multiple representations.

* Grep files for pattern

* Execute Sugar CLI command

Check if file is a code file

Get display name with emoji for a skill.

* Find files in directory

Check if a path is protected and should never be modified

Normalize text for comparison.

* Filter by severity

Comprehensive diagnostic for skill issues. Args: skill_path: Path to skill directory Returns: dict: Diagnostic report w

Calculate Jaccard similarity between two sets.

* Collect source files

Determine how to resolve a specific conflict

Parse markdown content into sections

Check if file should be ignored

* Check if this finding blocks deployment

Calculate overall similarity using multiple methods.

* Execute command and return result

Extract meaningful keywords from text

Extract meaningful words from text.

Identify obsolete skills based on usage patterns.

Generate update suggestions based on verification results

* Get blockers only

* Get severity level (1-4, lower is worse)

List all emoji assignments.

Load the skills registry.

Load and parse skill markdown file

* Update task status in dependency table

Comprehensive skill validation including structure and registry check. Args: skill_path: Path to skill directory Returns:

Validate SKILL.md YAML frontmatter format and required fields. Args: skill_path: Path to skill directory Returns: tuple

Validate that a skill is properly registered in skills.json. Args: skills_json_path: Path to skills.json file skill_name: Na

Validate skill directory structure. Args: skill_path: Path to skill directory Returns: tuple: (is_valid, error_message)

Analyze a configuration file

Analyze directory contents

Analyze which other skills reference this skill

Apply suggestion to file content

Assess the risk level of merging skills

Classify feature type based on name

Construct complete merged content from frontmatter and body

Recursively count keys in JSON object

Create update suggestion for a specific issue

Detect authentication methods

Detect build tool/bundler

Detect database technologies and patterns

Detect frontend/backend framework from dependencies

Detect Python framework from requirements

Detect state management solutions

Detect testing frameworks

Determine project type based on detected technologies

Execute directory creation

Execute delete operation

Execute file move operation

Extract API endpoint mentions from documentation

Extract code blocks from documentation

Extract configuration variable mentions

Extract domains from skill description and capabilities

Extract feature mentions

Extract file path references

Extract framework mentions from documentation

Extract links from documentation

Extract relevance domains based on project characteristics

Extract technology mentions from documentation

Find API endpoint definitions

Find deployment configuration files

Find files that would logically belong in a directory

* Format for console output

* Format for HTML

* Format for markdown

Generate a summary of the merge operation

Generate recommendation for trigger conflicts

Get last git modification date for a file

Determine appropriate directory for a file extension

Group overlapping skills into merge candidates

Load common stop words for text analysis

Load system state JSON

Load verification results JSON

Normalize trigger text for comparison

Parse dependency file for technology detection

Reconstruct merged body from sections

Resolve a specific conflict based on strategy

* Run built-in checks that don't require file parsing

Save operation log for audit trail

Check if two sections are similar enough to be considered the same

Suggest removing empty directories

Suggest addition of missing features documentation

Suggest moving non-essential files from root

Suggest creating missing standard directories