skills.rest
stellaromics
stellaromicsOFFICIAL
Explore all skills by this author →
GitHub

source-audit

Audit upstream library functions, helpers, tests, and git history before modifying code.

Updated Aug 23, 2026
Search Tags:#debugging#audit#code-review#git-history#tests#upstream#function-analysis
One-click install
npx skills add https://github.com/stellaromics/fast-bioinfo --skill source-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-audit
Source: https://github.com/stellaromics/fast-bioinfo/tree/main/.claude/agents/contributor/skills/source-audit
Command: npx skills add https://github.com/stellaromics/fast-bioinfo --skill source-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read and evaluate upstream library source code before proposing changes to determine what actually needs fixing and avoid introducing regressions.

Core Features & Use Cases

  • Read the target function, its helpers, and the tests to understand intent and coverage.
  • Inspect the git history for recent changes to identify context and drift.
  • Identify explicit vs implicit assumptions and risky design patterns before editing.

Quick Start

Summarize the target function, its helpers, tests, and recent history before making any changes.

Frequently Asked Questions about source-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit upstream library code before making changes?▼

To audit upstream library code, you read the target function, its helpers, and tests to understand intent, then inspect git history to identify context and drift before editing.

What is the best way to prevent regressions when modifying upstream source code?▼

Preventing regressions involves identifying explicit vs implicit assumptions and risky design patterns in the upstream source before editing, ensuring any changes are well-founded and safe.

Why should I inspect git history before fixing a bug in a dependency?▼

Inspecting git history surfaces recent changes, context, and drift in the dependency, helping you identify implicit assumptions and cross-version issues that could cause regressions.

How do I find implicit assumptions in helper functions before editing code?▼

Finding implicit assumptions requires reading the target function and its helpers to document chained calls and risky patterns, enforcing safe modifications based on actual code behavior.

Does source-audit work with tests to understand function intent?▼

Yes, source-audit reads the target function and its tests to understand intent and coverage, ensuring you know what actually needs fixing before proposing any upstream code changes.

Related Skills

Explore More Software Engineering Skills→
crycriMcrycriM

codebase-skeleton

Compress source code repositories into compact skeletons with imports and signatures.

Community
Intermediate
CyapstayeCyapstaye
9

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
peancharoenpeancharoen

speckit.checker

Run static analysis tools to detect linting, type, and security issues across source code.

Community
Advanced
shanevshanev
76

unslopify

Detect sloppy code patterns across TypeScript/JavaScript, Go, and Rust.

Community
Basic