visualize-harness

Map package, app, and component relationships into interactive HTML graphs.

27|1|Updated Jan 26, 2026

Search Tags:#dependency analysis #repository #system architecture #harness #visualize

Ready to run

npx skills add https://github.com/hua-bang/pulse-agent --skill visualize-harness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: visualize-harness
Source: https://github.com/hua-bang/pulse-agent/tree/main/harness/skills/visualize-harness
Command: npx skills add https://github.com/hua-bang/pulse-agent --skill visualize-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintainers visualize the repository harness, including the relationship between packages, apps, and other components, making it easier to understand the structure and dependencies.

Core Features & Use Cases

Visualize Repository Harness: Show the repository harness as an interactive HTML graph.
Custom Scope: Visualize the harness for specific packages, apps, or the entire repository.
Reading Path: Trace the flow of knowledge and evidence through the harness.
Metrics: Present current filesystem metrics and bilingual reading paths.
Use Case: For a package with complex dependencies, visualize the harness to see how its components interact and identify any potential bottlenecks.

Quick Start

Use the visualize-harness skill with the following command to visualize the harness for the package 'pulse-coder-engine':

visualize-harness --scope pulse-coder-engine

Frequently Asked Questions about visualize-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I visualize repository dependencies as an interactive HTML graph?▼

You can visualize repository dependencies by running a script that maps the relationships between packages, apps, and components, generating an interactive HTML graph to illustrate the system architecture. It requires JSON data and Node.js to execute.

What is the best way to analyze the system architecture of a complex package?▼

Analyzing system architecture of a complex package involves mapping its internal dependencies and component interactions. This approach visualizes the repository harness, helping maintainers identify potential bottlenecks and trace reading paths through the system.

Can I visualize the dependency graph for a specific package scope instead of the entire repository?▼

Yes, you can visualize the dependency graph for a specific package scope. By defining a custom scope in your command, the visualization focuses solely on the relationships within that targeted package or app, rather than the entire repository.

Do I need Node.js to render interactive HTML graphs for repository dependencies?▼

Yes, Node.js is required to render interactive HTML graphs for repository dependencies. The visualization process relies on executing rendering scripts built in Node.js to process the required JSON data and display the final graph.

What dependencies are needed to map component relationships in a repository harness?▼

To map component relationships in a repository harness, you need JSON data representing the structure and Node.js installed to run the rendering scripts. No external library dependencies are required beyond the provided scripts.

How do I trace the reading path of knowledge through a repository harness?▼

To trace the reading path of knowledge through a repository harness, you generate an interactive HTML graph that presents current filesystem metrics and bilingual reading paths, showing the flow of evidence and knowledge between components.