cycle

Run a sub-agent swarm cycle to discover codebase issues.

6|3|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/jamesaphoenix/tx --skill cycle-jamesaphoenix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cycle
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/cycle
Command: npx skills add https://github.com/jamesaphoenix/tx --skill cycle-jamesaphoenix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a coordinated sub-agent swarm to discover codebase issues such as bugs, anti-patterns, and potential security concerns, reducing manual review effort.

Core Features & Use Cases

  • Distributed scanning: parallel agents examine code modules and dependencies for defects.
  • Convergence-driven discovery: rounds refine findings until no new significant issues arise.
  • Guarded execution: enforces usage of the tx cycle CLI over dangerous team tools and prompts.

Quick Start

Run the cycle CLI to start a sub-agent swarm scan of the codebase for issue discovery.

Frequently Asked Questions about cycle

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

FAQPage Schema
How do I automate codebase scanning to discover bugs and security issues?

Automated codebase scanning uses a sub-agent swarm to examine modules and dependencies in parallel, surfacing bugs, anti-patterns, and security concerns. It runs iterative rounds until convergence, reducing manual review effort by generating actionable tasks for each finding.

What is convergence-driven issue discovery and how does it work?

Convergence-driven issue discovery runs iterative scanning rounds that refine findings until no new significant code issues arise. Each round narrows the scope, filtering false positives and deepening analysis of confirmed bugs and anti-patterns across modules and dependencies.

How do I run a sub-agent swarm to scan my codebase for anti-patterns?

Run the tx cycle CLI to start a sub-agent swarm scan of the codebase. The swarm distributes parallel agents across modules and dependencies to detect anti-patterns, bugs, and security concerns, generating actionable tx tasks for each discovered issue.

Can I use parallel agents to scan code modules and dependencies for defects?

Yes, distributed scanning deploys parallel agents to examine code modules and dependencies simultaneously for defects. The swarm coordinates agents across the codebase, iteratively refining results until convergence to ensure comprehensive issue coverage.

Does the cycle CLI require any dependencies or external tools to run?

The cycle CLI operates with no external dependencies. It enforces guarded execution by using the tx cycle CLI exclusively, avoiding dangerous team tools and prompts while generating actionable tx tasks for discovered codebase issues.

When should I avoid using a sub-agent swarm for code review?

Avoid sub-agent swarm code review when you need real-time interactive analysis or have a very small codebase where manual review suffices. The swarm is designed for comprehensive scanning across modules and dependencies, which may be excessive for trivial projects.