- Home
- Skills
- Technical Documentation
- Repository Feature Map
Works with the AI Agents you already use
Repository Feature Map
Trace existing feature ownership, contracts and tests before adding code. Get a scoped reuse decision and an evidence-linked documentation plan.
$9
Repository Feature Map
Example session with this skill installed
Fictional example. Docs say export available. Supplied descriptions: API calls ExportService; service checks owner permission and writes durable outbox; provider translates payloads; worker consumes outbox. Default flag false. Duplicate-request unit test passes; no live provider acceptance. Map reuse for adding a provider and propose docs corrections without edits. Actual source access absent.
- Read your context and instructions
- Compiled the repository feature map
Extend the existing export path with the new provider. The supplied descriptions point to ExportService as the business owner; a second export service would risk duplicating its permission and durable-request boundary.
This is a provisional map based entirely on fictional descriptions you supplied. I have not inspected the repository, run tests, or checked a deployed environment.
| Evidence | What it supports | Limit |
|---|---|---|
src/api/export.ts calls ExportService | API entry point delegates export behavior | API contract and exact call symbol are unavailable |
src/export-service.ts checks owner permission and writes a durable outbox | Service owns permission decisions and request persistence | Storage schema, transaction boundaries and other eligibility rules are unknown |
src/provider.ts translates payloads | Provider translation belongs at the adapter boundary | Interface, registration and provider selection are unknown |
| Worker consumes the outbox | Existing asynchronous delivery path should be reused | Worker path, retries and delivery-state writes are not supplied |
| Duplicate-request unit test reportedly passes | Some duplicate-request behavior has unit coverage | Test body and execution evidence are unavailable; this does not prove provider delivery |
| Default flag is false; no live-provider evidence | Default configuration is gated and provider acceptance remains unverified | Actual deployment flag value and runtime availability are unknown |
Keep owner permission checks and durable outbox creation in ExportService. Preserve the duplicate-request behavior covered by the existing test. Add provider-specific payload translation through the existing adapter interface and connect it through the existing provider selection and worker path once those interfaces are inspected. Do not move domain decisions or introduce a parallel queue or service merely to add a provider. Durable request state is represented by the outbox; downstream delivery-state authority is still unknown. UI ownership and any separate contracts or database models are not established by the supplied material.
Before implementation, inspect src/provider.ts and its callers, the ExportService implementation, worker consumer, outbox model, flag configuration and duplicate-request test. These are the smallest useful sources for confirming registration, idempotency, failure handling and the extension point. No new implementation is proposed beyond the provider extension until those boundaries are confirmed.
The documentation's unqualified “available” claim is not supported by this evidence. Proposed correction: “Export implementation is described and duplicate-request unit coverage is reported. The feature defaults to disabled. Deployment configuration and live-provider acceptance remain unverified.” This does not establish that every deployment is disabled. Apply the correction to the existing canonical feature document and its index entry together when editing is authorized; their paths were not supplied. Keep the new provider marked as proposed until implemented and accepted.
Required verification includes existing permission and duplicate-request regressions, adapter payload and error behavior, worker delivery and failure handling, and durable state across retries where the existing contract requires them. Authorized environment acceptance must establish configuration and successful end-to-end provider delivery, including the visible downstream result if there is an affected screen. No live provider action is authorized here. I have made no edits or external changes.
All scenario data is fictional. No live operations were performed.
Connects securely to your tools. The creator never sees your data.
About this skill
Help your agent find the implementation that already owns a capability. Trace one user flow through contracts, services, provider adapters, jobs, durable state and tests. Separate source evidence from deployment assumptions, identify contradictions and propose the narrowest change. Includes a feature brief, capability-index row, discovery method and fictional worked example. Works with authorized repository access or supplied snippets; snippet-only maps remain provisional. No automatic commits or deployment.
Findings depend on the files or supplied snippets actually available. Missing source, configuration or live acceptance remains unknown. Codex fictional scenarios only; no guarantee of exhaustive repository coverage or correctness. No automatic commits or deployments.
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 22 days ago
Permissions
Reads bundled Markdown and authorized repository files or supplied snippets. Writes only scoped feature documentation when explicitly requested. No network, accounts, credentials, production operations or automatic commits are required.