1C ERP Diagnostics

Plugin one-c-erp-diagnostics in akim-kaneyev/1c-erp-diagnostics. Commands read from the repo's manifest — 18 days ago.

Skills (33)

• one-c-erp-access-rights

  Diagnose and redesign 1C:ERP user access with least privilege, preserving business functions while removing unnecessary administrative capabilities.

• one-c-erp-action-decision

  Select the smallest safe reversible action after a 1C:ERP cause has been verified or define the next evidence request when it has not.

• one-c-erp-artifact-extraction

  Safely extract and inventory sanitized 1C CF/CFE/EPF artifacts without running untrusted BSL or loading them into an information base.

• one-c-erp-capability-discovery

  Build a current-session capability map before selecting tools, skills, plugins or execution paths for a 1C:ERP case.

• one-c-erp-case-state

  Maintain resumable Gate 1-10 state for a 1C:ERP investigation across long sessions and project handoffs.

• one-c-erp-code-analysis

  Analyze supplied 1C code, queries, SKD definitions or extensions and connect code behavior to observed ERP movements/results without inventing metadata.

• one-c-erp-companion-plugins

  Safely coordinate the verified 1C companion ecosystem—Unica, 1C Skills and optional Jev—plus host-managed document, repository, UI and sandbox capabilities without fabricating availability or dependencies.

• one-c-erp-compare-documents

  Compare a correct and problematic 1C:ERP document or two states dimension-by-dimension and identify differences that may explain the symptom.

• one-c-erp-cost-month-close

  Diagnose 1C:ERP cost calculation, cost deviations and month-close incidents from evidence, including registrar tracing and before/after validation.

• one-c-erp-data-safety

  Minimize confidentiality risk when analyzing 1C:ERP exports, databases, credentials and business documents with AI tools or sandboxes.

• one-c-erp-diagnose-core

  Build the evidence-first causal chain for a 1C:ERP incident and determine the earliest demonstrated divergence.

• one-c-erp-diagnostics

  Single dynamic entrypoint for evidence-first Gate 0-10 orchestration across 1C:ERP data, code, releases, a verified Unica/1C Skills/Jev ecosystem and controlled actions.

• one-c-erp-dynamic-plan

  Convert a routed 1C:ERP case into a bounded dependency graph of specialist analyses, executable validations and review gates.

• one-c-erp-evidence-intake

  Inventory and rank 1C:ERP evidence such as movements, registers, postings, reports, screenshots, XLSX, PDF, MXL exports and code before diagnosis.

• one-c-erp-evidence-synthesis

  Merge specialist outputs into a claim-to-evidence graph while preserving contradictions, uncertainty and provenance.

• one-c-erp-final-review

  Perform scoped Gate 10 review, close only the declared goal when eligible, and keep unresolved linked 1C incidents explicitly open or blocked.

• one-c-erp-goal-contract

  Define a concrete, verifiable goal and stop condition for a 1C:ERP diagnostic case before investigation begins.

• one-c-erp-incident-search

  Search the public Infoblog title index for non-authoritative 1C incident leads while preserving source provenance, freshness state and case-data boundaries.

• one-c-erp-local-static-analysis

  Discover, run and capture provenance from local SonarQube BSL analysis without exposing credentials or treating static findings as ERP causality.

• one-c-erp-official-source-check

  Verify time-sensitive or normative 1C, tax, platform, release and methodology claims against current official sources before using them in a diagnostic conclusion.

• one-c-erp-open-source-intake

  Review an open-source 1C or agent tool before adding it to the diagnostics ecosystem.

• one-c-erp-plugin-audit

  Audit the dynamic 1C ERP Diagnostics plugin and unified companion marketplace for manifest integrity, orchestration completeness, source provenance, dependency honesty and safety controls.

• one-c-erp-post-change-validation

  Validate a 1C:ERP correction by comparing the same analytics before and after, not merely by disappearance of an error message.

• one-c-erp-post-item-expenses

  Diagnose 1C:ERP post-item expense allocation, unallocated balances, expense analytics and allocation-base mismatches.

• one-c-erp-production

  Diagnose 1C:ERP production, stages, materials, output, returns, repair and related analytical-chain breaks.

• one-c-erp-release-difference

  Compare 1C platform/configuration releases and determine whether a documented change can explain the observed case behavior.

• one-c-erp-risk-control

  Classify and control the blast radius of tools and proposed changes in 1C:ERP diagnostics.

• one-c-erp-route-case

  Route a 1C:ERP incident to the correct diagnostic domain by observed symptom, with at most one justified secondary domain.

• one-c-erp-sandbox-execution

  Decide when isolated execution such as OpenSandbox materially helps a 1C:ERP diagnostic and control it safely.

• one-c-erp-settlements

  Diagnose 1C:ERP receivables, payables, advances, offsets and settlement-analytics mismatches by chronological registrar tracing.

• one-c-erp-vat

  Diagnose 1C:ERP VAT records, purchase/sales books, tax-period corrections and duplicates with current official-source verification when normative claims matter.

• one-c-erp-verify-conclusion

  Independently challenge a preliminary 1C:ERP root-cause conclusion before it can be marked final.

• one-c-erp-warehouse-series-assignments

  Diagnose 1C:ERP warehouse, series, assignment and analytical-key breaks that create missing, split, negative or unexpected stock/value.

Similar plugins