ls-thinker

Review code and architectural patterns to produce structured advisory reports.

Updated Aug 5, 2026

Search Tags:#analysis #risk assessment #architecture review #read-only #codebase inspection #design recommendations #lite suite

Ready to run

npx skills add https://github.com/ahostbr/liteharness --skill ls-thinker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ls-thinker
Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-thinker
Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-thinker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the need for fast, high-signal analysis of codebases, architectures, and design tradeoffs without allowing the agent to modify files.

Core Features & Use Cases

Read-only investigation: Performs analysis by reading and inspecting existing code and system context without editing, writing, or modifying files.
Structured advisory output: Produces a consistent report with a summary, key findings, prioritized recommendations, and risks/concerns when relevant.
Bootstrap for LiteSuite Thinker role: Establishes the agent’s identity and canvas linkage so analysis requests can be registered and sent back to the requester.

Quick Start

Register the ls-thinker agent, ask it to analyze the provided repository or design description, and then request a structured report focused on findings, prioritized recommendations, and risks.

Frequently Asked Questions about ls-thinker

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

FAQPage Schema

How do I perform a read-only architecture review without modifying my codebase?▼

Read-only architecture review inspects existing code and system context without editing files to provide design critique and risk assessment. The analysis generates structured outputs covering summaries, findings, recommendations, and concerns.

What is risk-aware advisory for codebase inspection?▼

Risk-aware advisory for codebase inspection identifies architectural patterns and design tradeoffs to deliver prioritized recommendations and concerns. It evaluates existing systems in read-only mode to ensure no files are modified during analysis.

How do I get structured design recommendations for existing systems?▼

Structured design recommendations are produced by reviewing code and architectural patterns to output a consistent report. This report includes a summary, key findings, prioritized recommendations, and identified risks or concerns.

Can I use this for design critique and codebase inspection across LiteSuite sessions?▼

Design critique and codebase inspection are supported across LiteSuite sessions by registering the agent and establishing canvas linkage. This allows analysis requests to be registered, processed in read-only mode, and sent back to the requester.

Does codebase inspection require non-edit permissions?▼

Codebase inspection requires strict non-edit permissions to ensure the agent performs analysis by reading and inspecting existing code without writing or modifying files. This constraint guarantees safe, read-only investigation of system context.

What are the limitations of read-only architecture analysis?▼

Read-only architecture analysis is limited to inspecting and reviewing existing code without editing, writing, or modifying files. It cannot implement changes or fix identified risks, focusing solely on delivering advisory outputs and recommendations.