> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.rightbrain.ai/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.rightbrain.ai/_mcp/server. # Templates for Tech & Data > Task templates for code analysis, data processing, and technical documentation Technology and data teams use Rightbrain Tasks to automate code analysis, data processing, and technical documentation. Below are ready-to-use task templates with configuration details. #### Code Analysis #### Security Vulnerability Scanner **Purpose:** Identify security vulnerabilities and insecure coding practices in source code **Inputs:** * Source code files or snippets * Programming language and framework * Security standards to apply (OWASP, CWE) * Known vulnerability database **Task Instructions:** ``` Analyse {source_code} and identify security vulnerabilities including SQL injection risks, XSS vulnerabilities, authentication flaws, data exposure issues, and insecure dependencies. Provide specific remediation guidance for each vulnerability found. ``` **Outputs:** * Vulnerabilities identified with severity ratings * CWE classifications * Affected code locations (line numbers) * Remediation suggestions and secure code examples * Overall security risk score **Integration:** Pre-commit hook, pull request creation, scheduled security scans, block merge if critical issues **Try it now** #### Code Review **Purpose:** Provide improvement suggestions and identify issues in pull requests or code changes **Inputs:** * Code changes or diff * Programming language and style guide * Project context and patterns * Review criteria checklist **Task Instructions:** ``` Review {code_changes} and analyse code quality, best practice compliance, performance implications, and maintainability. Provide actionable improvement suggestions. ``` **Outputs:** * Code quality assessment * Best practice violations identified * Performance and maintainability concerns * Documentation gaps * Specific improvement recommendations with examples **Integration:** Pull request opened, code committed to review branch, post review comments, assign priority labels **Try it now** #### Data Processing #### Data Quality Validation **Purpose:** Validate dataset integrity, completeness, and compliance with schema and business rules **Inputs:** * Dataset to validate (CSV, JSON, database extract) * Schema definition or data dictionary * Validation rules and quality thresholds * Reference data for lookups **Task Instructions:** ``` Validate {dataset} for completeness, identifying any missing fields. Ensure provided fields are in the correct format and within reasonable ranges. ``` **Outputs:** * Quality score (0-100) * Issues categorised by field and severity * Row-level errors with specific locations * Summary statistics (completeness, accuracy, consistency) * Remediation recommendations **Integration:** Data import, ETL pipeline stage, accept clean data, quarantine invalid records, generate quality report **Try it now** #### Data Anomaly Detection **Purpose:** Identify unusual patterns, outliers, and quality issues in datasets **Inputs:** * Dataset to analyse * Historical baseline data or patterns * Anomaly detection thresholds * Expected data distributions **Task Instructions:** ``` Analyse {dataset} for anomalies by comparing against the entire dataset. Identify statistical outliers, pattern breaks, trend deviations, and unexpected values. ``` **Outputs:** * Anomalies detected with severity classifications * Statistical analysis (standard deviations, percentiles) * Anomaly type and affected records * Potential root causes * Investigation priority recommendations **Integration:** Real-time data stream, scheduled batch analysis, alert data team, quarantine anomalous records **Try it now** #### Log Analysis **Purpose:** Extract insights, errors, and patterns from system logs for troubleshooting and monitoring **Inputs:** * Log files or entries * Log format specification * Known error patterns or signatures * Normal operation baselines **Task Instructions:** ``` Analyse {log_files}. Extract errors, warnings, and critical events. Identify patterns indicating system issues, performance degradation, or security concerns.Correlate related log entries to trace issues. Summarise key findings and recommend troubleshooting steps. ``` **Outputs:** * Error and warning summary with counts * Critical events and patterns identified * Performance or security concerns flagged * Correlated event sequences * Troubleshooting recommendations **Integration:** Scheduled log analysis, alert threshold exceeded, create incident tickets, update monitoring dashboard **Try it now** #### Technical Documentation #### PR Summary Generator **Purpose:** Generate both technical and non-technical summaries from pull requests, making code changes accessible to any audience. ***Inputs:*** Pull request or commit details ***Task Instructions:*** ``` Analyse {pull_request} and generate two summaries. For the technical summary, detail the code changes, affected components, and implementation approach. For the non-technical summary, explain what changed in plain language, why it matters, and the impact on users or the business. ``` Outputs: * Technical summary (code changes, components affected, implementation details) * Non-technical summary (plain-language explanation, user/business impact) **Integration:** Post to Slack channel, update release notes, notify engineering and product teams **Try it now** #### Changelog Generation **Purpose:** Summarise code changes, features, and fixes for release notes and version documentation **Inputs:** * Git commit history or pull request list * Versioning scheme * Change categorisation rules * Previous changelog for context **Task Instructions:** ``` Generate changelog entry based on a {commit}. Categorise changes into features, bug fixes, improvements, breaking changes, and deprecations. Write user-friendly descriptions for each change, highlighting impact and migration requirements. ``` **Outputs:** * Structured changelog by category * User-friendly change descriptions * Breaking changes and migration guide * Contributors list * Version comparison summary **Integration:** Release branch created, version tagged, update changelog file, publish release notes **Try it now** ## Resources #### [Create a Task](/api-reference/api-reference/tasks/tasks/list-tasks) Complete API reference for task execution #### [API Integration](/docs/quickstart/create-a-task) Create and configure a Task over the API #### [Agent patterns](/docs/patterns/agents) Give agents focused tools for conditional technical work