Pequi
Official@pequiproject · Brazil
Plataforma de Busca Ativa de Hanseníase no estado de Alagoas
Agent Skills by Pequi
Showing 9 vetted skills indexed across 1 GitHub repositories.
PequiProjectcode-review
Identify code-quality issues, security vulnerabilities, and maintainability gaps in pull requests.
PequiProjectpull-request
Automate GitHub pull request creation with compliance checks and structured descriptions.
PequiProjectgitflow
Organize and enforce GitFlow branching for feature, release, and hotfix workflows.
PequiProjecttdd-workflow
Enforce a test-driven development workflow with RED and GREEN validation.
PequiProjectrelease-manager
Plan and coordinate end-to-end software releases for the Pequi project.
PequiProjectbug-investigation
Diagnose and repair bugs in the Pequi codebase with structured evidence-driven analysis.
PequiProjectconventional-commits
Guide teams to craft conventional commit messages with types and scopes.
PequiProjectarchitect-reviewe
Identify architectural strengths, gaps, and risk drivers in system designs.
PequiProjectsecurity-review
Identify and mitigate security vulnerabilities across web and backend services.
Frequently Asked Questions About Pequi
FAQPage SchemaWhat specific engineering tasks does Pequi enable?▼
Pequi enables rigorous code quality enforcement, automated pull request governance, and structured bug investigation. It facilitates architectural risk assessment, security vulnerability mitigation, and standardized release coordination to ensure maintainability and compliance within the project codebase.
Which personas benefit from these engineering standards?▼
These standards are designed for software engineers, technical leads, and release managers working on the Pequi platform. The practices support developers maintaining high-integrity codebases, security auditors verifying system safety, and project leads coordinating feature deployments and hotfix cycles.
What are the prerequisites for implementing these standards?▼
Implementation requires a Git-based version control environment and a commitment to test-driven development practices. Teams must adopt the defined branching strategies and commit message conventions to ensure compatibility with the existing validation and release management processes.