access-analyzer

Extract and manage Access database objects with Git-backed automation.

7|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/lunasoft2001/github-copilot-access-analyzer --skill access-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: access-analyzer
Source: https://github.com/lunasoft2001/github-copilot-access-analyzer/tree/main/skill-bundle
Command: npx skills add https://github.com/lunasoft2001/github-copilot-access-analyzer --skill access-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, microsoft-access-automation, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Microsoft Access projects often suffer from fragmentation between on-disk databases and code, making audits, refactoring, and collaboration error-prone. This Skill consolidates analysis, export, refactoring planning, and re-import workflows into a repeatable, version-controlled process for .accdb/.mdb databases.

Core Features & Use Cases

  • End-to-end workflow: analyze, export, refactor planning, and re-import of Access objects (tables, queries, forms, reports, macros, VBA).
  • Git-backed exports: automatic commits, diffs, and a persistent export folder to enable traceability.
  • Auto-generated REFACTORING_PLAN.md to guide changes and track progress across teams.
  • Safety features include timestamped backups, dry-run modes, and detailed logging to reduce risk during operations.

Quick Start

Run the export script to generate a complete object export, create backups, and initialize a Git-backed workflow for tracking changes.

Frequently Asked Questions about access-analyzer

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

FAQPage Schema
How do I export Microsoft Access database objects for version control?▼

You can export Access database objects for version control by extracting tables, queries, forms, reports, macros, and VBA into a persistent folder, then using Git-backed automation to commit and track changes automatically.

What is the best way to plan a refactoring of an Access .accdb database?▼

The best way to plan a refactoring of an Access .accdb database is to use automation that analyzes objects and auto-generates a REFACTORING_PLAN.md file, guiding changes and tracking progress across teams.

Can I safely re-import VBA code and queries into an Access .mdb file after modifying it?▼

Yes, you can safely re-import VBA code and queries into an Access .mdb file through a scripted workflow that enforces timestamped backups, dry-run modes, and detailed logging to reduce risk during operations.

Does Git-backed Access automation support PowerShell integration?▼

Yes, Git-backed Access automation supports PowerShell integration, using scripted commands to manage exports, apply UTF-8 encoding, and enforce backup-before-operation rules for .accdb and .mdb workflows.

Why does my Access database refactoring lose track of changes across team members?▼

Access refactoring loses track of changes across team members when on-disk databases and code are fragmented, but Git-backed exports with automatic commits, diffs, and auto-generated plans consolidate the process for traceability.

What are the limitations of automating Access object exports without backups?▼

Automating Access object exports without backups risks data loss during operations, but this tool mitigates the limitation by enforcing backup-before-operation rules, timestamped backups, and dry-run modes for safe execution.