fullsend-ai
Official@fullsend-ai
Offers specialized engineering operations for GitHub-centric development, focusing on code review, release management, and technical documentation lifecycle maintenance.
Agent Skills by fullsend-ai
Showing 12 vetted skills indexed across 2 GitHub repositories.
customer-research
Identify affected customers and cohorts from GitHub issue labels.
issue-classification
Classify GitHub issues into exact workstream categories with confidence thresholds.
code-review
Analyzes code changes and produces a structured findings report.
code-implementation
Plan and execute GitHub issue fixes with tests and committed changes.
fix-review
Automate PR review feedback into code changes with tests and fix-result.json.
pr-review
Orchestrate GitHub PR reviews with context gathering and structured results.
cutting-releases
Automate release tagging, versioning, and GoReleaser publishing for GitHub workflows.
replay-session
Replay Claude Code sessions from GitHub Actions artifacts as interactive HTML.
Filing GitHub Issues
Create well-formed GitHub issues with labels and routing via gh CLI.
renumber-adr
Detect ADR numbering conflicts and renumber files before merging PRs.
writing-adrs
Create immutable Architecture Decision Records with context, decision, and consequences.
writing-user-docs
Create admin and user guides with structured procedures and cross-links.
Frequently Asked Questions About fullsend-ai
FAQPage SchemaWhat specific engineering tasks does fullsend-ai enable?▼
Fullsend-ai enables structured code reviews, automated pull request feedback implementation, Architecture Decision Record management, and release versioning. It also provides capabilities for classifying GitHub issues, generating technical documentation, and renumbering decision records to prevent merge conflicts.
Which personas benefit most from these capabilities?▼
These capabilities are designed for software engineers, DevOps practitioners, and technical leads who manage high-velocity repositories. It is particularly useful for teams seeking to standardize code quality, maintain immutable architectural history, and streamline the release process within GitHub environments.
What are the prerequisites for implementing these capabilities?▼
Implementation requires an active GitHub repository and appropriate permissions to manage pull requests, issues, and release artifacts. Users must have existing repository structures compatible with GoReleaser for publishing and standard Markdown formatting for Architecture Decision Records and user documentation.