uloop-get-logs

Retrieve and filter Unity Console log entries as JSON.

500|44|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/hatayama/unity-cli-loop --skill uloop-get-logs-hatayama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uloop-get-logs
Source: https://github.com/hatayama/unity-cli-loop/tree/main/.agents/skills/uloop-get-logs
Command: npx skills add https://github.com/hatayama/unity-cli-loop --skill uloop-get-logs-hatayama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve and inspect Unity Console logs to quickly find errors, warnings, and relevant stack traces so you can diagnose build and runtime issues faster.

Core Features & Use Cases

  • Filtered Retrieval: Select logs by type (Error, Warning, Log, All) to focus on relevant messages.
  • Search & Regex: Perform text or regex searches across messages and optionally within stack traces to pinpoint failures.
  • Configurable Output: Limit the number of returned entries, include stack traces when needed, and receive results as JSON for tooling or automation integration.
  • Use Case: After running a build or automated test suite, run this command to extract recent error logs containing a specific exception pattern and export them for triage.

Quick Start

Run uloop get-logs with desired filters to retrieve and export Unity console entries as JSON for debugging.

Frequently Asked Questions about uloop-get-logs

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

FAQPage Schema
How do I retrieve Unity console logs and filter them by error type via CLI?

To retrieve Unity console logs, use the CLI to filter entries by type (Error, Warning, Log, All) and output the results as JSON. This allows you to quickly isolate specific error messages during debugging or post-build verification.

Can I search Unity stack traces using regex to pinpoint specific runtime exceptions?

Yes, you can search Unity stack traces using regex. The tool applies text or regex searches across log messages and optionally within stack traces to help pinpoint specific runtime exceptions and failures.

What is the best way to extract Unity error logs for automated test triage?

The best way to extract Unity error logs for automated test triage is to run a CLI command that filters by error type, limits the maximum count, and exports the console entries as JSON for integration with automation tooling.

Does this Unity log filtering tool require any specific project path setup?

No specific project path setup is required, but you can provide an optional project path parameter. This allows the command to target a specific Unity project directory when retrieving and filtering console logs.

How do I limit the number of Unity console log entries returned during debugging?

You can limit the number of Unity console log entries returned by configuring the maximum count parameter. This restricts the JSON output to a manageable number of recent errors, warnings, or traces for faster diagnosis.