Codexqa Code Analyzer logo

Codexqa Code Analyzer

Organization
openqa-cn
codexqa-code-analyzer

Queries a local CodexQA symbol graph for change review, regression scope, test gaps, error location, and entry risk. Use when the user mentions codexqa-code-analyzer, code-analyzer, codexqa, 符号图, 代码知识图谱, 建索引, 查调用, 影响面, --diff-base, 变更审查, 回归范围, 测试缺口, or asks to install / run the codexqa CLI (index, query). Former skill name: code-analyzer. Not CodexQA evidence-pack HTML review (that is codexqa-code-reviewer), not SAST + Agent LLM Detection code-risk scan reports (that is codexqa-defect-analyzer), and not architecture wiki reports (that is codexqa-code-wiki), and not full exception RCA reports (that is codexqa-rootcause-analyzer).

Overview

Publisheropenqa-cn
Repositorycodexqa
Skill namecodexqa-code-analyzer
Stars
233
Forks
3
Bundled files
8
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 8 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by openqa-cn on GitHub. Read the source before you install it.

Installation

Install the Codexqa Code Analyzer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/openqa-cn/codexqa/tree/main/skills/codexqa-code-analyzer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/openqa-cn/codexqa.git /tmp/codexqa
mkdir -p .claude/skills
cp -r /tmp/codexqa/skills/codexqa-code-analyzer .claude/skills/codexqa-code-analyzer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Codexqa Code Analyzer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Codexqa Code Analyzer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Codexqa Code Analyzer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Code Analyzer

Local symbol graph for quality work: index first, then answer what changed, who is hit, what is untested, and where an error comes from.

There is no codexqa diff or codexqa review. Review a change with:

text
index --diff-base <ref>  →  change-groups  →  symbol-diff  →  callers / tests / entries

Pick the scenario before acting. Do not query or review a diff until an index exists. Do not run full-text search unless the user asked. README.md / README.zh-CN.md are human-facing. Do not load them at runtime.

Documents (load on demand)

Read this file first. Read another file only when the row below applies. Do not preload the whole tree.

FileLoad when
SKILL.md (this file)always: routing, report contract, reject conditions
references/playbook.mdentering a scenario (index health / change / defect / implementation / architecture)
references/diagrams.mdbefore drawing; copy init and classDef verbatim
references/cli.mdCLI missing, PATH, LLM, or maintenance
references/mcp.jsongraph-query tool schema is needed
README.md, README.zh-CN.mdhuman-facing; not needed by the agent

Scenario routing

Open references/playbook.md and jump to the named section.

User is asking…Playbook section
Review a PR / what changed / vs mainReview one change (index health first)
Who is hit / what to regression-testRegression scope under that change section
Any unit tests / coverage gapsTest gaps under that change section
Which HTTP / RPC / MQ path reaches thisEntry risk under that change section
Auth, payments, password, tokenSensitive paths under that change section
Logs, stack, error text, commentsLocate a defect
How does this function work / who calls itUnderstand an implementation
Module ownership / wrong layerArchitecture drift
Results are empty / every change is defaultIndex health / Analysis blockers

Report contract

Deliver a Mermaid evidence report (graph conclusions + diagrams). Not a product review, and not Archify / interactive HTML. Read references/diagrams.md before drawing. A diagram that misses the quality bar fails the report.

Report body is only these blocks:

  • Must-read groups (by risk)
  • What changed (trust only symbol-diff / file-source vs file-base)
  • Must-test callers / entries (must come from edges / reach / path / tagged)
  • Test gaps (a tests directory is not a tests edge)
  • Sensitive paths (write "none" if there are none)
  • Diagrams: at least one, and it must pass the quality bar

Reject the whole report and rewrite if any of these hold:

  • Written as a generic project review (product intro, use cases, scored pros/cons)
  • Evidence comes from README / a website / guesswork, not this run of summary / imports / source / edges / reach / change-groups / symbol-diff
  • Only names large files or high fan-in; never uses edges / reach to say who is hit
  • Infers "covered" from a tests directory name; never checked tested_count or reach --direction in --edge-kinds tests
  • Mermaid is missing the Claude paper init, the three classDef lines, or a core module that should be risk has no class ... risk
  • Architecture subgraph titles are package names (Renderer / Compiler / Shared) instead of Entry → Application → Domain → Storage
  • Interactive HTML / Archify canvas was generated (this skill does not ask for that)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Codexqa Code Analyzer AI skill do?

Queries a local CodexQA symbol graph for change review, regression scope, test gaps, error location, and entry risk. Use when the user mentions codexqa-code-analyzer, code-analyzer, codexqa, 符号图, 代码知识图谱, 建索引, 查调用, 影响面, --diff-base, 变更审查, 回归范围, 测试缺口, or asks to install / run the codexqa CLI (index, query). Former skill name: code-analyzer. Not CodexQA evidence-pack HTML review (that is codexqa-code-reviewer), not SAST + Agent LLM Detection code-risk scan reports (that is codexqa-defect-analyzer), and not architecture wiki reports (that is codexqa-code-wiki), and not full exception RCA report...

Why use Codexqa Code Analyzer on TypingMind?

Because you install it once and use it with any model. Codexqa Code Analyzer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Codexqa Code Analyzer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/openqa-cn/codexqa/tree/main/skills/codexqa-code-analyzer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Codexqa Code Analyzer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Codexqa Code Analyzer?

As many as you like. As long as a model supports skills, you can use Codexqa Code Analyzer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Codexqa Code Analyzer AI skill free?

Yes. It is published on GitHub by openqa-cn under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇