github.com/logseq/logseq (link)

commit signals (363)

source signals (82)

• .claudedirectoryvia claude-code
• clj-e2e/AGENTS.mdvia agents-md

  # E2E test Guide
  
  - Source Layout (`src/logseq/e2e/`)
    - `assert.clj`: Custom assertion functions
    - `block.clj`: Block manipulation helpers
    - `config.clj`: Configuration settings
    - `const.clj`: Shared constants
    - `graph.clj`: Graph management helpers
    - `keyboard.clj`: Keyboard shortcut helpers
    - `locator.clj`: Playwright locator utilities
    - `page.clj`: Page operations helpers
    - `playwright_page.clj`: Playwright page initialization
    - `rtc.clj`: RTC testing helpers
    - `settings.clj`: Logse

• libs/guides/AGENTS.mdvia agents-md

  # AGENTS.md - Logseq Plugin Development Guide
  
  ## Overview
  
  This document provides guidance for AI agents (Copilot, coding assistants, etc.) to help develop Logseq plugins using
  the `@logseq/libs` SDK.
  
  Logseq is a privacy-first, open-source knowledge management and note-taking application built on top of local plain-text
  Markdown and Org-mode files. The plugin system extends Logseq's functionality through a JavaScript/TypeScript SDK.
  
  ## Repository Structure
  
  ### Core SDK (`logseq/logseq` - `libs/` folder)

• cli-e2e/AGENTS.mdvia agents-md

  # cli-e2e
  
  Shell-first end-to-end tests for logseq CLI.
  
  ## Test cli-e2e itself
  - Run internal cli-e2e harness unit tests: `bb unit-test`
  
  ## cleanup first
  - Execute cleanup: terminate stale db-worker-node processes, terminate stale db-sync listeners on port `18080`, and remove cli-e2e temp roots: `bb cleanup`
  - Preview cleanup actions only (no kill/delete): `bb cleanup --dry-run`
  
  ## Run non-sync suite
  - List declared non-sync case ids: `bb list-cases`
  - Run non-sync cases with build preflight unless `--sk

• cli/AGENTS.mdvia agents-md

  - Do not modify any files under `spec/` during development unless explicitly asked to modify the `.mli` files under `spec/`.
  - Do not modify any dune file during development unless explicitly asked.
  - If development is blocked because the `.mli` definitions under `spec/` are unclear or unreasonable, stop development immediately and report the specific spec issue, suggested changes, and rationale.
  - This repository implements only the CLI portion. It does not include the db-worker-node server, and should use

• src/main/logseq/cli/AGENTS.mdvia agents-md

  # logseq CLI
  
  ## Dev rules
  - Ensure `--output json`, `--output edn`, and `--output human` produce reasonable, consistent, and user-friendly output.
  - Ensure all command outputs are user/agent-friendly, especially error outputs.
  - Do not implement new `thread-api` in db-worker unless it is absolutely necessary.
  - Use logseq-cli skill; test the changed parts with the new-built logseq-cli & db-worker-node server.
  - Ensure at least all cli-e2e non-sync cases passed.
  
  ## Debug tools
  - `--verbose` - debug cli pro

• AGENTS.mdvia agents-md

  # Repository Guidelines
  
  ## Build, Test, and Development Commands
  - `bb dev:lint-and-test` runs linters and unit tests.
  - `bb dev:test -v <namespace/testcase-name>` runs a single unit test (example: `bb dev:test -v logseq.some-test/foo`).
  - App E2E tests live in `clj-e2e/`; run from that directory with `bb test` (or `bb -f clj-e2e/bb.edn test` from repo root).
  - CLI E2E tests live in `cli-e2e/`; run with `bb -f cli-e2e/bb.edn test --skip-build` (or `bb -f cli-e2e/bb.edn build` first when needed).
  - If a req

• .agents/skills/esm-cjs-risk-scan/SKILL.mdvia unspecified

  ---
  name: esm-cjs-risk-scan
  description: Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims. Use when changing Electron/main-process dependencies, debugging startup import errors, or auditing packages before dependency upgrades.
  ---
  
  # ESM/CJS Risk Scan
  
  Scan Node/Electron ClojureScript code for npm dependencies that may fail at runtime due to ESM/CJS incompatibility. Use w

• .agents/skills/logseq-debug-workflow/SKILL.mdvia unspecified

  ---
  name: logseq-debug-workflow
  description: Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps.
  ---
  
  # Logseq Debug Workflow
  
  Use for any Logseq bug investigation.
  
  ## Core rule
  
  Treat this as a debugging workflow, not a code-only change.
  
  Before claiming a fix, you must:
  
  1. Choose the correct *runtime repl* and say why:
     - `:app` for renderer, DOM, UI, frontend state
     - `:electron` for main-process, BrowserWindow, IPC, app config
     - `:db-work

• .agents/skills/logseq-server-usage-stats/SKILL.mdvia unspecified

  ---
  name: logseq-server-usage-stats
  description: Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the `deps/db-sync` scripts and D1 schema. Use when requests involve `show-usage-stats`, server usage reporting, active-entity counting, or Cloudflare D1 cost impact of usage tracking.
  ---
  
  # Logseq Server Usage Stats
  
  Use this skill to run and explain server usage stats for db-sync.
  
  ## Run stats
  
  Use the packaged co

• .agents/skills/logseq-i18n/SKILL.mdvia unspecified

  ---
  name: logseq-i18n
  description: "Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings. Use when: writing UI code with hardcoded text, adding new user-facing strings, editing translation dict files, reviewing i18n compliance, working with notification/show!, adding translatable UI attributes, or any task involving src/resources/dicts/. Also use when the user mentions i18n, translation, localization, or hardcoded strings."
  ---
  
  # Logseq i18n Skill
  
  ## Wh

• .agents/skills/logseq-dependency-upgrade/SKILL.mdvia unspecified

  ---
  name: logseq-dependency-upgrade
  description: Audit, plan, and refresh dependency upgrades for the Logseq repository by scanning every non-gitignored package.json, deps.edn, bb.edn and nbb.edn manifest, checking latest upstream versions, cross-root consistency, lockfile resolution, deprecation, staleness, and OSV vulnerabilities, then generating a batch-ordered upgrade plan and compact JSON artifact.
  ---
  
  # Logseq Dependency Upgrade
  
  Use this skill when the task is to audit dependencies, build an upgrade

• .agents/skills/logseq-repl/SKILL.mdvia unspecified

  ---
  name: logseq-repl
  description: Start and coordinate Logseq development REPL workflows for the Desktop renderer `:app`, Electron main-process `:electron`, and `:db-worker-node` runtimes through one unified workflow.
  ---
  
  # Logseq REPL Workflow
  
  Use this skill when the user needs a Logseq development REPL for:
  
  - Desktop renderer `:app`
  - Electron main process `:electron`
  - `:db-worker-node`
  - any combination of those runtimes
  
  The workflow uses one shared state directory: `<repo>/tmp/logseq-repl/`.
  
  ## S

• .agents/skills/logseq-review-workflow/SKILL.mdvia unspecified

  ---
  name: logseq-review-workflow
  description: Review Logseq code changes, PRs, patches, commit ranges, or implementation plans through one main-agent orchestration workflow that routes read-only subagents across independent review passes, then deduplicates, validates, and reports findings for the web app, desktop app, and Logseq CLI.
  ---
  
  # Logseq Review Workflow
  
  ## Core principle
  
  The main agent drives the review. It identifies scope, loads routing rules, launches independent read-only subagents for each 

• libs/SKILL.mdvia unspecified

  ---
  name: logseq-plugin-sdk
  description: Build, debug, or review Logseq plugins with the `@logseq/libs` SDK (TypeScript/JavaScript, iframe/shadow sandboxed). Use when the task involves writing plugin entry code, registering slash/command/UI items, provideUI/provideStyle/provideModel, settings schema, macro renderers, DB-graph properties & tags, Datascript/DSL queries, experimental APIs, theme plugins, or the `logseq/*` CLJS facade generated under this package.
  ---
  
  # Logseq Plugin SDK Skill
  
  This skill gove

• .agents/skills/logseq-cli-maintenance/SKILL.mdvia unspecified

  ---
  name: logseq-cli-maintenance
  description: Improve readability, consistency, and long-term maintainability of Logseq CLI-related code, command flows, and tests.
  ---
  
  # logseq-cli-maintenance
  
  ## Purpose
  
  Use this skill when working on Logseq CLI-related code and you want to improve:
  
  - Readability
  - Maintainability
  - Consistency across command modules
  - Long-term development ergonomics
  
  This skill focuses on practical refactoring and guardrails, without changing behavior unless explicitly requested.
  
  ---

• .agents/skills/logseq-review-workflow-eval/SKILL.mdvia unspecified

  ---
  name: logseq-review-workflow-eval
  description: Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a structured delta. Use when evaluating whether changes to .agents/skills/logseq-review-workflow improved review quality, coverage, validation rigor, subagent orchestration, or false-positive rate.
  ---
  
  # Logseq Review Workflow Eval
  
  ## Overview
  
  Use this skill to evaluat

• .agents/skills/logseq-rest-api/SKILL.mdvia unspecified

  ---
  name: logseq-rest-api
  description: Call the Logseq semantic REST API (db-sync worker) with a graph-scoped personal access token, including E2EE-encrypted graphs. Use when writing integrations, scripts, or agent tooling that read or write Logseq DB graphs over HTTP, when working with `logseq_pat_` tokens, or when debugging API behavior on encrypted vs plain graphs.
  ---
  
  # Logseq Semantic REST API
  
  Use this skill to operate the semantic REST API served by the db-sync Cloudflare
  worker (local dev: `node de

• .agents/skills/logseq-cli/SKILL.mdvia unspecified

  ---
  name: logseq-cli
  description: Operate the current Logseq command-line interface to inspect or modify graphs, pages, blocks, tasks, tags, and properties; run Datascript queries; show page/block trees; manage graphs; and manage db-worker-node servers. Use when a request involves running `logseq` commands or interpreting CLI output.
  ---
  
  # Logseq CLI
  
  ## Overview
  
  Use `logseq` to inspect and edit graph entities, run Datascript queries, and control graph/server lifecycle.
  
  ## Quick start
  
  - Run `logseq --he

• .agents/skills/logseq-answer-machine/SKILL.mdvia unspecified

  ---
  name: logseq-answer-machine
  description: Answer user questions about the Logseq repository by researching source code, docs, tests, runtime behavior, and local tools. Use when Codex needs to explain how Logseq works, why behavior happens, where logic lives, how CLI/Desktop/Web flows interact, or what evidence supports an answer, without implementing features or fixing bugs.
  ---
  
  # Logseq Answer Machine
  
  Use this skill to answer questions from the Logseq repo itself. Produce evidence-backed explanations,

• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified
• .agentsdirectoryvia unspecified

ignorefile signals (0)

none