Arx-Game
Official@arx-game
Offers specialized engineering governance for Django database optimization, GitHub repository integrity, and codebase surface classification.
Agent Skills by Arx-Game
Showing 8 vetted skills indexed across 1 GitHub repositories.
Arx-Gamerunning-tests
Guide SQLite and Postgres test workflows with just wrappers and tag decisions.
Arx-Gameworkflow-friction-audit
Log recurring tool-call failures and environment quirks into a persistent friction log.
Arx-Gamegithub-operations
Enforce canonical GitHub issue or PR numbers from gh create output for mutations.
Arx-Gamecodebase-indexing
Regenerate MODEL_MAP.md from Django model relationships via introspection script.
Arx-Gamesharedmemory-model
Enforce SharedMemoryModel imports for Django models to prevent N+1 queries.
Arx-Gameverify-against-code
Inspect codebases to classify surfaces as BUILT, NOT WIRED, or ABSENT.
Arx-Gamegrounding-before-action
Enforce solo tool calls and echo-back before follow-on actions.
Arx-Gameissue-to-merged-pr
Automate GitHub issue-to-PR workflows with CI feedback and post-merge cleanup.
Frequently Asked Questions About Arx-Game
FAQPage SchemaWhat specific tasks does Arx-Game enable for developers?▼
Arx-Game enables developers to enforce strict Django model relationships, prevent N+1 database queries via SharedMemoryModel, and maintain repository hygiene by linking GitHub issues to PRs. It also provides systematic classification of codebase surfaces to identify missing or unlinked components.
Which engineering personas benefit from these capabilities?▼
Backend engineers, database administrators, and technical leads managing Django-based architectures benefit most. These capabilities are designed for teams requiring rigorous enforcement of database query standards and consistent repository management practices across complex, multi-contributor codebases.
What are the prerequisites for implementing these repository operations?▼
Implementation requires an existing Django environment and a GitHub-integrated development lifecycle. Users must ensure their codebase supports Django model introspection and that their environment allows for the enforcement of specific import patterns and issue-tracking metadata.