saitoco
Official@saitoco
Offers GitHub-integrated governance for issue lifecycle management, requirement specification, and codebase drift detection.
Agent Skills by saitoco
Showing 10 vetted skills indexed across 1 GitHub repositories.
saitocomerge
Squash-merge approved pull requests and delete remote branches via gh CLI.
saitocoverify
Validate post-merge acceptance criteria and update GitHub Issue checkboxes.
saitocoauto
Automate GitHub issue lifecycle phases from discovery through verification.
saitocospec
Convert GitHub issue requirements into implementation plans with acceptance criteria.
saitococode
Automate GitHub issues into code work items with test verification.
saitocotriage
Automate GitHub issue triage and metadata maintenance with JSON output.
saitocoaudit
Detect drift and fragility between steering documents and codebases.
saitocoissue
Create and refine GitHub issues with acceptance criteria and verification patterns.
saitocoreview
Coordinate acceptance criteria verification and multi-perspective reviews on GitHub pull requests.
saitocodoc
Govern steering and project documents with frontmatter-driven templates and drift detection.
Frequently Asked Questions About saitoco
FAQPage SchemaWhat specific tasks does Saitoco enable for engineering teams?▼
Saitoco enables the systematic management of GitHub issues, including automated triage, requirement specification, and acceptance criteria verification. It facilitates the transition from discovery to implementation by linking steering documentation directly to code work items and ensuring consistency through drift detection.
Which personas benefit most from these GitHub-integrated capabilities?▼
Engineering leads, project managers, and technical contributors benefit from these capabilities. The functionality is designed for teams requiring strict adherence to acceptance criteria, standardized issue lifecycle phases, and automated governance between project documentation and repository state.
What are the prerequisites for implementing these governance patterns?▼
Implementation requires an active GitHub environment where issues and pull requests serve as the primary source of truth. Users must maintain steering documents with frontmatter-driven templates to enable the drift detection and verification patterns provided by the suite.