skills.rest
logseq
logseqOFFICIAL
Explore all skills by this author →
Website𝕏@logseqGitHub

logseq-answer-machine

Answers Logseq repository questions with evidence from source code, tests, and runtime probes.

44.7k|2.8k|Updated May 23, 2020
Search Tags:#REPL#code investigation#Logseq#ripgrep#repository analysis#read-only#evidence-backed answers
One-click install
npx skills add https://github.com/logseq/logseq --skill logseq-answer-machine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logseq-answer-machine
Source: https://github.com/logseq/logseq/tree/main/.agents/skills/logseq-answer-machine
Command: npx skills add https://github.com/logseq/logseq --skill logseq-answer-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers exploring the Logseq codebase often need accurate, evidence-backed explanations of how features work, where logic lives, and why behavior occurs, without risking accidental code changes during investigation.

Core Features & Use Cases

  • Evidence-Backed Investigation: Searches source files, tests, docs, migrations, and configs with ripgrep to build a precise evidence map of namespaces, call chains, and data flows.
  • Read-Only Guardrails: Enforces strict no-implementation rules, reverting any temporary probes or logs before delivering the final answer.
  • Runtime Verification: Coordinates CLI, REPL, Chrome, and Desktop UI probes when static analysis is insufficient to confirm behavior.
  • Use Case: Ask why a specific Logseq command behaves unexpectedly, and receive a structured outline citing exact files, line references, test coverage, and verified runtime results.

Quick Start

Use the logseq-answer-machine skill to explain how Logseq's CLI sync flow works, citing the source files and tests that prove it.

Frequently Asked Questions about logseq-answer-machine

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

FAQPage Schema
How do I find where a Logseq feature is implemented in the source code?▼

Use ripgrep to search for symbols, namespaces, routes, commands, and UI labels across the repository. The skill builds an evidence map linking the owning file, caller chains, relevant tests, and docs so another engineer can verify each claim.

How to verify Logseq runtime behavior without modifying code?▼

Load the logseq-cli or logseq-repl skills to run focused CLI commands or REPL probes against the correct target. Use disposable graphs for mutating commands, and record exact commands and outputs as verification evidence.

Can this skill fix bugs or implement features in Logseq?▼

No, the skill is strictly read-only and refuses implementation, bugfix, refactoring, or migration work. If a question turns into a change request, it stops and hands off to the appropriate implementation workflow.

Does the investigation cover Logseq Desktop and Electron internals?▼

Yes, it covers the Desktop renderer, Electron main process, db-worker-node, web app, CLI, and mobile surfaces. REPL probes target the correct runtime, and the Chrome or computer-use skills handle browser and Desktop UI observation.

What happens to temporary logging added during investigation?▼

Any temporary logs, probes, or config changes must be minimal, explained, and fully reverted before the final answer. The skill requires re-checking the diff to confirm the worktree is clean.

Related Skills

Explore More Software Engineering Skills→
phucle297phucle297

build-mcpb

Package a local MCP server with its runtime into a standalone .mcpb executable.

Community
Intermediate
andrewnovykovandrewnovykov

bug-fix

Automate the end-to-end bug fix workflow from investigation to validated fix.

Community
Advanced
testdoubletestdouble
198

refactor

Refactor code iteratively with test-gated validation after each step.

Official
Advanced
thrawn01thrawn01
11

surface-testing

Test HTTP endpoints, CLIs, and library exports without internal calls.

Community
Advanced