audit-config-paths

Audit Windows path handling and settings loading for OneDrive-backed Z: drive portability.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ElPoot/contabilidad --skill audit-config-paths
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-config-paths
Source: https://github.com/ElPoot/contabilidad/tree/main/.agents/skills/audit-config-paths
Command: npx skills add https://github.com/ElPoot/contabilidad --skill audit-config-paths

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies fragile Windows path and configuration dependencies that can break the contabilidad workflow when the OneDrive-backed Z: drive is missing, not mounted, or not initialized correctly.

Core Features & Use Cases

  • Path and portability audit: Checks whether the app relies on hardcoded Windows paths (especially Z:/Z:) outside the central configuration layer.
  • Startup flow validation: Verifies what happens during boot when Z: is unavailable, including whether a setup fallback UI is used or the app exits early.
  • settings.json resilience review: Assesses how missing or corrupt settings are handled via get_setting() to ensure the app can recover or fail gracefully.
  • Use Case: If a client runs the app on a machine where OneDrive is not yet synced or Z: is not mounted, this audit helps pinpoint why the app fails and what code paths must be made more robust.

Quick Start

Ask the auditor to scan the repository for hardcoded Z: or C:\ user paths outside gestor_contable/config.py, then verify the Z: mounting and get_setting() fallback behavior during startup.

Frequently Asked Questions about audit-config-paths

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

FAQPage Schema
How do I audit Windows paths for OneDrive portability issues?

To audit Windows paths for OneDrive portability, scan repository code for hardcoded Z: drive references outside the central configuration layer. This identifies fragile path dependencies that break workflows when the OneDrive-backed Z: drive is missing or not mounted.

Why does my app fail when the OneDrive Z: drive is missing?

Your app fails when the OneDrive Z: drive is missing because of hardcoded Windows paths and unvalidated startup flows. When Z: is unavailable, the app lacks a setup fallback UI, causing boot failures and portability crashes.

How do I check settings.json resilience when the file is corrupt or absent?

To check settings.json resilience, verify how the get_setting() function handles missing or corrupt configuration data. A robust implementation ensures the app recovers gracefully or fails safely instead of crashing when settings.json is unavailable.

How do I validate startup flow when a network drive is not mounted?

To validate startup flow when a network drive is not mounted, examine the boot sequence to see if a GUI setup fallback is triggered. This verifies whether the app attempts recovery or exits early when the Z: dependency is unavailable.

Does this path audit work with subst network drive mounting code?

Yes, this path audit works with subst network drive mounting code. It examines repository code paths that mount drives and read settings via get_setting(), reporting findings solely from actual code evidence in the specified configuration and GUI modules.