- Home
- Skills
- Technical Documentation
- Feature Understanding Report
Feature Understanding Report
Generate source-linked technical reports mapping feature logic, data flow, and unhandled failure paths.
$2.99
Works with the AI Agents you already use
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
| Step | Source Location | Logic/Behavior | Evidence/Missing Handling |
|---|---|---|---|
| Request Initiation | src/components/Upload.tsx:42 | Uses fetch with FormData. No explicit headers set for Content-Type. | Browser defaults to multipart/form-data with boundary. |
| Route/Auth | server/routes/user.js:110 | Uses authenticateToken middleware. Checks req.user.id. | Authorization failure returns 401; no redirect logic found. |
| Validation | server/controllers/userController.js:15 | Checks req.file.mimetype against ['image/jpeg', 'image/png']. | Missing: No file size limit check before buffer processing. |
| External Call | server/services/s3Service.js:22 | Calls s3.upload() with a 5s timeout. | Success returns Location string. Failure path for timeout is unhandled. |
| Persistence | server/models/User.js:85 | db.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
fileSizelimit in themulterconfiguration atserver/routes/user.js. - Wrap the
s3.uploadcall in atry/catchblock to handle network timeouts. - Update the UI to handle the 401 Unauthorized status explicitly.
Upload.tsx
TSX · React component
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
- Target Identification starts with a specific entry point or user action to limit scope.
- Dependency Tracing follows the request through routes and storage nodes using evidence-backed inspection.
- Logic Evaluation tests guards and expressions against specific input combinations.
- 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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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