Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

devsql-querying

Estrelas173

Forks11

Atualizado11 de junho de 2026 às 00:05

Query and analyze Claude Code + Codex CLI history joined with Git data and source code using SQL. Use when user asks about conversation history, productivity patterns, commit correlation, session analytics, codebase analysis, symbol search, file context, or impact analysis.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

douglance

douglance/devsql

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

Execute qualquer Skill com um clique

name	devsql-querying
description	Query and analyze Claude Code + Codex CLI history joined with Git data and source code using SQL. Use when user asks about conversation history, productivity patterns, commit correlation, session analytics, codebase analysis, symbol search, file context, or impact analysis.

DevSQL Querying Skill

Query Claude Code and Codex CLI history joined with Git commits and source code to analyze productivity patterns and understand codebases.

When to Use

User asks "How many Claude sessions did I have this week?"
User wants to "Find my longest debugging sessions"
User asks "Which prompts led to the most commits?"
User wants productivity analytics or session insights
User asks about correlating Claude/Codex usage with Git history
User wants to search for symbols, functions, or classes in the codebase
User asks "What's in this file?" or needs file context
User wants to understand what changed between commits
User asks about imports, dependencies, or impact of a file

Prerequisites

Ensure devsql is installed:

brew install douglance/tap/devsql

Agent Tool Commands

For structured queries, prefer these subcommands (they return JSON):

Command	Use When
`devsql search "<query>"`	Finding symbols by name (functions, classes, structs). Supports `--kind` filter and `--limit`.
`devsql context <file>`	Getting file metadata + all symbols defined in a file.
`devsql history <file>`	Showing Git commit history for a specific file with diff stats.
`devsql diff <base> <head>`	Comparing two Git refs with file-level and symbol-level change analysis.
`devsql impact <file>`	Analyzing a file's exports and finding potential dependents via imports.

All commands accept --repo / -r and --data-dir / -d options.

Available Tables

Claude/Codex Tables

Table	Columns
`history`	timestamp, display (prompt text), project, pastedContents
`jhistory`	session_id, ts, text, display, timestamp
`codex_history`	Alias of `jhistory`
`transcripts`	type, content, tool_name, session_id, _source_file, _session_id, _project, _agent_id, timestamp, model, usage_input_tokens, usage_output_tokens, usage_cache_read_input_tokens, usage_cache_creation_input_tokens, usage_ephemeral_5m_input_tokens, usage_ephemeral_1h_input_tokens, usage_service_tier
`sessions`	session_id, project, cwd, git_branch, version, title, first_timestamp, last_timestamp, user_message_count, assistant_message_count, subagent_count, total_input_tokens, total_output_tokens, total_cache_read_input_tokens, total_cache_creation_input_tokens, pr_url, pr_number
`todos`	content, status

transcripts covers ~/.claude/projects/<slug>/**/*.jsonl (top-level sessions plus subagent transcripts) and the legacy ~/.claude/transcripts/*.jsonl. sessions has one aggregated row per session file; _project / project is the project slug directory (e.g. -Users-you-Developer-app), NULL for legacy files. _agent_id is set only on subagent rows.

Git Tables

Table	Columns
`commits`	id, message, summary, author_name, authored_at, short_id
`branches`	name, is_head, commit_id
`diffs`	commit_id, files_changed, insertions, deletions
`diff_files`	commit_id, path, status (A/D/M/R/C), insertions, deletions

Code Tables (Source Analysis)

Table	Columns
`source_files`	path, name, extension, directory, size_bytes, line_count, modified_at, language
`source_lines`	file_path, line_number, content, is_blank
`symbols`	file_path, name, kind, line_start, line_end, signature, visibility, parameters, return_type, language
`imports`*	file_path, line_number, module, name, alias, kind, is_default, is_wildcard
`ast_nodes`*	(requires tree-sitter-ast feature)

* Full extraction requires the tree-sitter-ast build feature. Without it, symbols uses regex-based extraction and imports/ast_nodes are empty.

Supported languages for symbol extraction: Rust, TypeScript, JavaScript, Python, Go.

Symbol kinds: fn (Rust), function (TypeScript/JavaScript/Python), struct, enum, trait, type, const, static, mod, macro, class, interface (varies by language).

Approach

Understand what the user wants to analyze
Choose the right tool:
- For structured queries about symbols/files/history → use a subcommand
- For cross-table analytics or custom joins → compose a SQL query
Execute with: devsql "<query>" or devsql <subcommand> <args>
Present results with insights

Note: history.timestamp is in milliseconds. Use datetime(timestamp/1000, 'unixepoch') to convert.

Example Queries

-- Recent prompts
SELECT display as prompt, project
FROM history ORDER BY timestamp DESC LIMIT 10;

-- Prompts this week
SELECT COUNT(*) as prompts
FROM history
WHERE datetime(timestamp/1000, 'unixepoch') > date('now', '-7 days');

-- Correlate prompts with commits
SELECT
  date(c.authored_at) as day,
  COUNT(DISTINCT h.timestamp) as prompts,
  COUNT(DISTINCT c.id) as commits
FROM commits c
LEFT JOIN history h
  ON date(c.authored_at) = date(datetime(h.timestamp/1000, 'unixepoch'))
GROUP BY day
ORDER BY day DESC
LIMIT 14;

-- Which prompts led to commits?
SELECT h.display as prompt, COUNT(c.id) as commits_after
FROM history h
JOIN commits c ON date(datetime(h.timestamp/1000, 'unixepoch')) = date(c.authored_at)
GROUP BY h.display
ORDER BY commits_after DESC
LIMIT 10;

-- Tool usage
SELECT tool_name, COUNT(*) as uses
FROM transcripts
WHERE type = 'tool_use'
GROUP BY tool_name
ORDER BY uses DESC;

-- Find all public Rust functions (Rust emits kind='fn'; JS/TS use 'function')
SELECT name, file_path, line_start, signature
FROM symbols
WHERE kind = 'fn' AND visibility = 'pub'
ORDER BY file_path, line_start;

-- Top sessions by cache-read tokens
SELECT title, project, total_cache_read_input_tokens, last_timestamp
FROM sessions
ORDER BY total_cache_read_input_tokens DESC
LIMIT 10;

-- Daily output tokens by model (flattened usage columns)
SELECT DATE(timestamp) as day, model, SUM(usage_output_tokens) as output_tokens
FROM transcripts
WHERE type = 'assistant' AND usage_output_tokens IS NOT NULL
GROUP BY day, model
ORDER BY day DESC;

-- Codebase overview by language
SELECT language, COUNT(*) as files, SUM(line_count) as total_lines
FROM source_files
GROUP BY language
ORDER BY total_lines DESC;

-- Files with the most symbols
SELECT s.file_path, f.language, COUNT(*) as symbol_count
FROM symbols s
JOIN source_files f ON s.file_path = f.path
GROUP BY s.file_path
ORDER BY symbol_count DESC
LIMIT 10;

-- Most changed files correlated with symbol count
SELECT df.path, COUNT(DISTINCT df.commit_id) as commits,
  SUM(df.insertions) as total_adds,
  (SELECT COUNT(*) FROM symbols s WHERE s.file_path = df.path) as symbols
FROM diff_files df
GROUP BY df.path
ORDER BY commits DESC
LIMIT 10;

Output Formats

Default: formatted table
CSV: devsql -f csv "<query>"
JSON: devsql -f json "<query>"

name	devsql-querying
description	Query and analyze Claude Code + Codex CLI history joined with Git data and source code using SQL. Use when user asks about conversation history, productivity patterns, commit correlation, session analytics, codebase analysis, symbol search, file context, or impact analysis.