Feature Understanding Report

    1

    Generate source-linked technical reports mapping feature logic, data flow, and unhandled failure paths.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Feature Understanding Report

    Example session with this skill installed

    Analyze the /api/upload-profile-picture endpoint logic. Trace the data from the multipart/form-data request to the S3 upload and database update. Highlight any missing error handling.

    • Read your context and instructions
    • Compiled the feature understanding report
    • Generated the UI component

    I have traced the logic for the /api/upload-profile-picture feature from the client-side request through the backend processing.

    Feature Understanding Report: Profile Picture Upload

    StepSource LocationLogic/BehaviorEvidence/Missing Handling
    Request Initiationsrc/components/Upload.tsx:42Uses fetch with FormData. No explicit headers set for Content-Type.Browser defaults to multipart/form-data with boundary.
    Route/Authserver/routes/user.js:110Uses authenticateToken middleware. Checks req.user.id.Authorization failure returns 401; no redirect logic found.
    Validationserver/controllers/userController.js:15Checks req.file.mimetype against ['image/jpeg', 'image/png'].Missing: No file size limit check before buffer processing.
    External Callserver/services/s3Service.js:22Calls s3.upload() with a 5s timeout.Success returns Location string. Failure path for timeout is unhandled.
    Persistenceserver/models/User.js:85db.users.update() sets profile_url.Success message sent before DB promise resolution is verified.

    Logic Evaluation: Failure Paths

    Invalid Mimetype: If a .gif is uploaded, the controller returns a 400 error. The UI correctly displays "Unsupported Format".

    S3 Timeout: If the S3 upload exceeds 5 seconds, the promise hangs. There is no try/catch block around the upload service call in the controller, potentially leading to a Node.js process crash or orphaned request.

    Database Conflict: If the user ID is missing during the update, the DB driver returns an error that is logged but not sent to the client, resulting in a perpetual loading state.

    Documentation Conflict

    The docs/api-spec.md states that this endpoint returns a 413 error for large files. However, the code contains no file size validation, meaning the request will likely time out at the proxy level or exhaust memory before returning 413.

    Next steps

    • Implement a fileSize limit in the multer configuration at server/routes/user.js.
    • Wrap the s3.upload call in a try/catch block to handle network timeouts.
    • Update the UI to handle the 401 Unauthorized status explicitly.

    Upload.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Tracing the logic of a legacy feature is time-consuming and prone to assumptions. This skill parses source code to generate plain-English handoff reports that map data flow, identify failure paths, and flag discrepancies between code and documentation.

    What it does

    • Data Flow Mapping traces dependencies from entry points through validation, storage, and response cycles.
    • Edge Case Analysis identifies specific failure paths based on input values rather than generic error categories.
    • Documentation Auditing highlights direct conflicts between source code behavior and existing technical docs.
    • Request Profiling distinguishes between configured request options and default browser behaviors.
    • Missing Context Discovery flags absent error handling or validation without fabricating UI outcomes.

    How it works

    1. Target Identification starts with a specific entry point or user action to limit scope.
    2. Dependency Tracing follows the request through routes and storage nodes using evidence-backed inspection.
    3. Logic Evaluation tests guards and expressions against specific input combinations.
    4. Report Generation delivers a concise map or deep handoff report with verified source citations.

    Frameworks & tools

    Works with any web application stack where source files (React, Node.js, Python, Go, etc.) are available for inspection. It relies on static analysis of request initiation, HTTP status handling, and promise fulfillment patterns.

    Why this beats prompting it yourself

    Generic prompts often hallucinate execution success or overlook silent failures in network requests. This skill enforces strict boundaries between source evidence and inference, ensuring you never mistake a success message for confirmed data persistence.

    Use cases

    • Feature Handoffs to get new developers up to speed on a specific module without manual walkthroughs.
    • Refactoring Preparation to map dependencies before making structural changes to a route.
    • Bug Investigation to isolate where a specific input bypasses validation guards.
    • Documentation Refresh to synchronize outdated READMEs with the current implementation.

    Known limitations

    Does not execute code, perform network requests, or access live databases. Analysis is limited to provided source files and does not guarantee complete system coverage or runtime accuracy.

    Does not execute code, run tests, or access live databases. Limited to static analysis of authorized source files. Cannot verify side effects like third-party API execution or email delivery.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    Permissions

    Read Files
    Listed10 days ago
    Updated8 days ago

    What's inside

    Frequently Asked Questions

    This skill performs static analysis on your codebase to create a plain-English map of how data moves through a specific feature, highlighting exactly where it might fail or where the code contradicts your existing documentation.

    It is compatible with any agent capable of file system access or repository reading, supporting major web stacks including React, Node.js, Python, and Go.

    No complex installation is required; once the skill is added to your agent, you simply provide the target entry point and access to the relevant source files to begin the analysis.

    You receive the full logic framework for generating reports, including specialized instructions for data flow mapping, edge case analysis, and documentation auditing.

    Because this skill relies on static analysis of provided source files rather than runtime execution, it cannot access live databases or trigger actual network requests to verify external API responses.

    Yes, the skill is designed to handle updates to your tech stack automatically, as it analyzes the logic patterns of the source code you provide rather than relying on a fixed version of a language.

    New in Technical Documentation