developers

Enforce FA v3 development rules, test policies, and audit procedures for the GeoSupply AI codebase.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill developers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developers
Source: https://github.com/ShubhamManachekar/GeoSupply/tree/main/.agent/skills/developers
Command: npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill developers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FA v3 development rules, test policies, and audit procedures establish a standardized, auditable framework for any developer interacting with the GeoSupply codebase, reducing risk and ensuring consistent quality.

Core Features & Use Cases

  • Enforces a ZERO MOCK policy to prevent certain mock usage during core component tests.
  • Defines dynamic discovery and audit requirements to validate schemas, workers, and agents before phase closures.
  • Outlines banned practices and verification steps to maintain code health and security across the GeoSupply project.

Quick Start

Review code changes for FA v3 rule compliance, run the dynamic audit workflow, and confirm readiness before merging.

Frequently Asked Questions about developers

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

FAQPage Schema
How do I enforce FA v3 development rules during GeoSupply code reviews?

To enforce FA v3 development rules during GeoSupply code reviews, apply the standardized audit framework to validate code changes, run the dynamic audit workflow, and confirm compliance before merging.

What is the ZERO MOCK policy for core component testing?

The ZERO MOCK policy is a strict testing constraint that prevents certain mock usage during core component tests to ensure consistent quality and auditable behavior within the GeoSupply FA v3 ecosystem.

Can autonomous agents and Copilot interact with the GeoSupply FA v3 codebase?

Yes, autonomous agents and Copilot can interact with the GeoSupply FA v3 codebase by following the defined dynamic discovery, banned practices, and formal verification steps to maintain code health and security.

How do I validate schemas, workers, and agents before phase closures?

To validate schemas, workers, and agents before phase closures, execute the prescribed audit command to perform dynamic discovery and verify formal compliance with FA v3 test policies.

What banned practices should I check for in GeoSupply software engineering audits?

During GeoSupply software engineering audits, check for explicitly banned practices and verify that all formal verification steps have been completed to maintain code health and security across the project.

Do I need to run an audit command before merging GeoSupply codebase changes?

Yes, you need to run the prescribed audit command before merging GeoSupply codebase changes to verify formal compliance with FA v3 development rules and ensure audit readiness.