trailofbits

Independently rerun an unchanged bug reproduction package before repair. Check whether compiler diagnostics or runtime assertions support the exact reported claim, then preserve execution evidence and record a confirmed, unconfirmed, or inconclusive judgment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Independently verify a bug reproduction before repair
• Recheck compiler errors or runtime assertions
• Document uncertain or unreliable reproduction evidence

Prepare a regression investigation by fixing the exact before and after source versions, preserving PR or commit context, and producing a sealed preparation record that explains change boundaries and evidence collection limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare source versions for a regression investigation
• Preserve PR discussions and review comments
• Document change boundaries and collection limits

Review a specific code change and trace its callers to identify behavior that may have broken. Record suspected regressions, reachable triggers, evidence needs, and coverage gaps so a separate reproduction step can investigate them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find possible regressions introduced by a code change
• Trace changed behavior to supported interfaces
• Organize candidates for reproduction

Independently reproduce a reported runtime or compiler bug in a local repository. Build the baseline, exercise the actual artifact or compiler, and save logs and structured records distinguishing reproduction, absence of the behavior, and setup blockers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reproduce a reported runtime bug locally
• Verify a compiler failure using its diagnostic
• Preserve logs and records for a reproduction handoff

Independently rerun supplied proof-of-concept code against freshly built versions from before and after a change. Compare observed behavior, verify reachability through real interfaces, and preserve separate logs showing agreement, divergence, or blockers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Independently check a supplied reproduction result
• Compare behavior before and after a change
• Verify reachability with the claimed access level

Assess source code and live reproduction evidence to decide whether a change introduced a regression, a newly caused defect. Record supported conclusions, exclusions, severity, and unresolved gaps in an evidence-linked decision file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Decide whether a change introduced a new defect
• Separate existing bugs from newly introduced defects
• Record missing evidence and unresolved questions

Build and run systems before and after a change, then execute the same reproduction procedure against both. Save environment details, inputs, commands, and separate logs to document observed behavior and any setup blockers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare behavior before and after a change
• Create a portable procedure to reproduce a suspected defect
• Record environments, commands, and execution logs

Coordinate investigations into regressions introduced by PRs or commits. Assign preparation, discovery, reproduction, independent verification, decisions, and reporting to separate stages, while preserving evidence and progress records for later resumption.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate regressions across PRs or commits
• Coordinate staged work across multiple agents
• Resume an investigation from saved progress

Repair one independently confirmed local bug by addressing the rule the code violates and checking related variants within scope. Deliver regression tests, before and after test results, separate patch files, and one local commit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Repair a local bug after independent confirmation
• Check related violations within the agreed repair scope
• Record test results and patches for review

Independently verifies a committed security patch by testing the original, patched, and fully reverted code. It preserves test evidence, checks the declared repair scope, and reports confirmed failures, missing evidence, and limits of what was proven.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Independently verify a security patch
• Compare original, patched, and reverted behavior
• Check valid inputs for regressions

Handle one known local bug or testable bug hypothesis through reproduction, independent validation, repair, and regression checks. Produce a local patch commit and evidence reports that help reviewers judge whether the fix is ready.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate and repair one reported local bug
• Have separate agents verify reproduction and the fix
• Prepare evidence reports for patch review

Turn saved regression decisions into evidence-linked HTML, Markdown, and JSON reports. Validate records and coverage, preserve assigned ratings, and distinguish confirmed defects from existing bugs, rejected claims, and unresolved work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compile saved decisions into a regression report
• Refresh reports after evidence or decisions change
• Review coverage gaps and unresolved findings

Diagnose Claude in Chrome connection failures on macOS by checking native messaging hosts, the processes linking Chrome to Claude, and their settings. It guides fixes for competing configurations, stale wrappers, and session conflicts, including restart steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate a browser extension connection error
• Restore browser integration after a Claude Code update
• Switch browser automation between Claude Code and Cowork

Writes and reviews Lean 4 proofs, machine-checked arguments for mathematics or specifications. Follows Mathlib conventions to organize definitions and lemmas, fill proof gaps, refactor lengthy proofs, and establish automated checks for unproved claims and style.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Formalizing mathematics or specifications in Lean 4
• Filling sorry placeholders in proofs
• Splitting long proofs into reusable lemmas

Find other occurrences of a known bug across a codebase by tracing its root cause. Gradually broaden search patterns, assess matching candidates, assign severity, and document findings with rules to help prevent recurrence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding similar issues after discovering a vulnerability
• Building CodeQL or Semgrep queries from a known bug
• Checking whether similar code shares the same root cause

Uses a known or suspected vulnerability to find related code through Trailmark's graph of calls, types, and implementations. Produces ranked review targets with reasons and limitations for follow-up security analysis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding variants of a known vulnerability
• Prioritizing code that shares sensitive operations
• Preparing candidates for Semgrep or CodeQL review

Get a quick structural overview of a codebase with Trailmark. The skill identifies programming languages, counts entry points where execution begins, and returns dependency information to support orientation before deeper analysis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting oriented in an unfamiliar codebase
• Checking languages and entry point counts before analysis
• Preparing a structural overview for Vivisect or Galvanize

Analyze code structure with Trailmark to identify complex functions, trace input flow, assess impact across connected code, and locate privilege boundaries. The resulting JSON provides detailed evidence for deciding where to focus a code audit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing code audit targets
• Tracing input flow and assessing impact
• Inspecting unresolved calls and type references

Turn a Mermaid sequence diagram of a cryptographic protocol into a ProVerif model, a file for formal security checks. It includes queries for secrecy, authentication, replay resistance, and forward secrecy where applicable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Converting a cryptographic protocol diagram into a .pv file
• Preparing session key secrecy checks
• Modeling authentication and replay resistance

Build a graph of functions and calls across multiple programming languages to investigate entry points, paths to sensitive operations, and potential impact. Use the results to prioritize security reviews and connect external findings with source code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing call paths from entry points to sensitive functions
• Prioritizing code for a security audit
• Connecting calls across language and RPC boundaries

Create dictionaries of keywords and identifying byte sequences for fuzzing, or testing with generated inputs. Extract useful entries from code, binaries, or specifications, then configure fuzzers to explore parsing paths beyond initial input validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a dictionary for JSON or XML parser fuzzing
• Add protocol keywords to generated test inputs
• Test image parsers with file signatures and chunk names

Create Mermaid diagrams from code relationships parsed by Trailmark. Visualize function calls, class inheritance, module dependencies, class members, complexity hotspots, and paths from inputs to sensitive functions, with adjustable focus, depth, and layout.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping function calls around a selected function
• Visualizing class inheritance and members
• Drawing module dependency maps

Set up OSS-Fuzz for an open-source project and test it locally. Prepare configuration and build files, run fuzz tests that probe code with varied inputs, reproduce reported crashes, and inspect which code the tests reach.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing an open-source project for OSS-Fuzz enrollment
• Testing an OSS-Fuzz build locally before submission
• Reproducing crashes from OSS-Fuzz reports

Helps set up and run cargo-fuzz for Rust projects using Cargo. Guides fuzz testing, which tries varied inputs, from writing test harnesses to detecting memory errors, reproducing crashes, and checking which code was exercised.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding fuzz tests to a Rust crate
• Generating structured test inputs
• Testing unsafe blocks or foreign-function calls