Contexter
Official@ctxr-dev · United States of America
OS for Agents
Agent Skills by Contexter
Showing 10 vetted skills indexed across 1 GitHub repositories.
dev-loop
Automates development issue lifecycle from branch creation to PR opening with two human gates.
release-tracker
Compute release umbrella status from linked development issues in GitHub.
issue-discovery
Guide staff engineers through multi-step issue discovery with session persistence.
tracker-sync
Synchronize issues, labels, and statuses across GitHub, Jira, Linear, and GitLab.
bootstrap-ops-config
Detect project context via git and GitHub, then generate a validated ops.config.json.
adapt-system
Propose cascading diffs across configuration and governance artifacts for user approval.
regression-handler
Automate regression triage by matching issues and generating a regression report.
plan-keeper
Enforce plan file placement, frontmatter integrity, and lifecycle transitions.
orchestrator
Standardize Captain-to-Soldier delegation briefings with governance rules for AI agents.
pr-iteration
Orchestrate end-to-end PR review cycles with external reviews and iterative fixes.
Frequently Asked Questions About Contexter
FAQPage SchemaWhat specific development tasks does Contexter enable?▼
Contexter enables end-to-end issue lifecycle management, including branch creation, PR opening, regression triage, and cross-platform synchronization. It standardizes delegation briefings for distributed teams and enforces governance rules for configuration and project artifacts.
Which engineering personas benefit most from these capabilities?▼
Staff engineers and release managers benefit most from these capabilities. The system is designed for technical leads who require oversight of multi-step issue discovery, release umbrella status tracking, and the enforcement of frontmatter integrity across complex project repositories.
What are the prerequisites for implementing Contexter in a repository?▼
Implementation requires an existing Git-based repository hosted on GitHub. The system relies on project context detection to generate ops.config.json files and requires established access permissions to synchronize data across external platforms like Jira, Linear, or GitLab.