JUXT
Official@juxt · UK
A Grid Dynamics company
Agent Skills by JUXT
Showing 14 vetted skills indexed across 2 GitHub repositories.
code-map
Build a cached JSON symbol and call-graph map using Language Server Protocol.
weed
Resolve divergences between Allium behavioral specification files and implementation code.
tend
Edit and validate Allium behavioral specification files against CLI tooling.
propagate
Generate unit, integration, property-based, and state machine tests from Allium behavioral specifications.
commit
Generate context-rich git commit messages with Chalk issue links.
tend-docs
Structure technical documentation with Diataxis quadrants and audience targeting.
chalk
Track GitHub issue work with structured comments and progress checklists.
pr
Synthesize commit history and issue comments into GitHub pull request descriptions.
voice
Standardize GitHub issues, pull requests, commits, and documentation with Diataxis-aligned writing.
weed-docs
Audit user-facing documentation for drift from code changes.
chill
Interrupts flawed software development workflows to reassess before resuming work.
allium
Generates executable specifications and integration tests from natural language descriptions of expected behavior, ensuring code aligns with stated requirements.
elicit
Guide structured conversations to define software specifications and edge cases.
distill
Extract formal Allium specifications from existing codebases.
Frequently Asked Questions About JUXT
FAQPage SchemaWhat specific tasks are enabled by JUXT's behavioral specification capabilities?▼
JUXT enables the generation of executable specifications from natural language, allowing for the creation of unit, integration, and state machine tests. It further supports resolving divergences between implementation code and stated requirements, ensuring that software behavior remains strictly aligned with formal specifications throughout the development lifecycle.
Which engineering personas benefit most from these technical capabilities?▼
Software architects, quality assurance engineers, and technical writers benefit from these capabilities. The system is designed for teams requiring rigorous alignment between business requirements, implementation code, and technical documentation, particularly in environments where maintaining consistency across large, evolving codebases is a critical operational requirement.
What are the primary prerequisites for integrating these capabilities into a repository?▼
Integration requires a codebase compatible with Language Server Protocol for symbol mapping and a structured approach to issue tracking via GitHub. Users must adopt the Allium specification format to define expected behaviors, which then serves as the foundation for generating tests, documentation audits, and commit metadata.