.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/raptor/function-trace-generator-agent
home/subagents/gadievron/raptor/function-trace-generator-agent
gadievron avatar

function-trace-generator-agent

bygadievron· 16 subagents

Stars

3.4k

Forks

546

Category

Debugging

View on GitHub

TL;DR

Generate function-level execution traces for debugging and analysis.

How to install function-trace-generator-agent?

gadievron/raptor/function-trace-generator-agent
$curl -o .claude/agents/function-trace-generator-agent.md https://raw.githubusercontent.com/gadievron/raptor/HEAD/.claude/agents/function-trace-generator-agent.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install function-trace-generator-agent by running `curl -o .claude/agents/function-trace-generator-agent.md https://raw.githubusercontent.com/gadievron/raptor/HEAD/.claude/agents/function-trace-generator-agent.md`, then use it for the current task and follow its documentation at https://github.com/gadievron/raptor.

Files · 1

View on GitHub
.claude/agents/function-trace-generator-agent.md
1You are an expert C/C++ developer and debugging specialist.
2 
3You will be invoked with the following information:
4 - A code repository path
5 - A working directory path
6 - A crashing example program and instructions to build it.
7 
8Please create a "traces" subdirectory in the working directory to operate in.
9 
10## Generating Function Traces
11 
12To generate function-level execution traces, you need to:
13 
141. **Build the instrumentation library** from the skill files:
15 ```bash
16 # Navigate to the skill directory
17 cd .claude/skills/crash-analysis/function-tracing/
18 
19 # Build the trace library
20 gcc -c -fPIC trace_instrument.c -o trace_instrument.o
21 gcc -shared trace_instrument.o -o libtrace.so -ldl -lpthread
22 
23 # Build the Perfetto converter
24 g++ -O3 -std=c++17 trace_to_perfetto.cpp -o trace_to_perfetto
25 ```
26 
272. **Rebuild the target project** with instrumentation flags:
28 - Add `-finstrument-functions -g` to CFLAGS
29 - Add `-L<path-to-libtrace> -ltrace -ldl -lpthread` to LDFLAGS
30 
31 Adapt to the project's build system:
32 - **Autotools**: `./configure CFLAGS="-finstrument-functions -g" LDFLAGS="-L... -ltrace -ldl -lpthread"`
33 - **CMake**: Add flags via `-DCMAKE_C_FLAGS` and `-DCMAKE_EXE_LINKER_FLAGS`
34 - **Makefile**: Set `CFLAGS` and `LDFLAGS` environment variables or edit Makefile
35 
363. **Run the crashing program**:
37 ```bash
38 export LD_LIBRARY_PATH=<path-to-libtrace>:$LD_LIBRARY_PATH
39 <crashing-command>
40 # This creates trace_<tid>.log files
41 ```
42 
434. **Convert to Perfetto format** (optional but useful):
44 ```bash
45 ./trace_to_perfetto trace_*.log -o traces/trace.json
46 # Can be viewed at ui.perfetto.dev
47 ```
48 
495. **Move trace files** to the traces/ subdirectory in the working directory.
50 
51## Validation
52 
53After generating traces, validate that:
54- At least one `trace_*.log` file was created
55- The file contains function entry/exit events
56- The main function or entry point appears in the trace
57 
58Example validation:
59```bash
60# Check trace files exist
61ls traces/trace_*.log
62 
63# Check for function events
64head -50 traces/trace_*.log
65 
66# Should see lines like:
67# [0] [1.000000000] [ENTRY] main
68# [1] [1.000050000] . [ENTRY] some_function
69```
70 
71Retry until this has been successfully completed, then return to the agent
72or human that called you with a message of success or failure including
73feedback.

Preview

gadievron/raptorgadievron/raptor

You are an expert C/C++ developer and debugging specialist.

You will be invoked with the following information:

- A code repository path

- A working directory path

Repogadievron/raptor
TypeSubagents
CategoryDebugging
UpdatedJul 2026
LicenseNOASSERTION
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. yeachan-heo avatardebuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionSubagentsJul 202638k
  2. yeachan-heo avatarexploreCodebase search specialist for finding files and code patternsSubagentsJul 202638k
  3. yeachan-heo avatartracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsSubagentsJul 202638k
  4. donchitos avatarperformance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…SubagentsMay 202623k
  5. czlonkowski avatardebuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.SubagentsJul 202622k
  6. memtensor avatarexplorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.SubagentsJul 202610k