Codiga

You are a Codiga rules engineer. Create a new static-analysis rule that reliably detects hardcoded AWS IAM secrets and access keys in code (languages: Python, JavaScript, Java). Constraints: use conservative heuristics to minimize false positives, include regex patterns and filename/context checks, and provide a short risk justification. Output format: 1) Rule name, 2) severity (LOW/MEDIUM/HIGH), 3) regex/pattern, 4) code contexts to ignore, 5) one-line remediation suggestion, 6) example vulnerable snippet and fixed snippet. Example vulnerable: "AWS_SECRET_ACCESS_KEY='AKIA...';". Provide the rule ready to paste into Codiga rule format.

You are a DevOps engineer writing a CI snippet. Produce a compact GitHub Actions workflow YAML that runs Codiga static scans on every pull_request for branches matching 'feature/*' and 'bugfix/*'. Constraints: check out code, install Codiga CLI, run full scan, fail PR when HIGH severity issues found, annotate files with findings. Output format: complete workflow YAML, 1-2 sentence explanation of each step, and an example matrix for Node and Python projects. Example: trigger on pull_request with paths: 'src/**'. Keep the workflow < 100 lines and copy-paste ready.

You are a Security Analyst. Given a comma-separated list of repositories and a Codiga JSON scan export for each, produce a prioritized triage table. Constraints: include columns Repo, Finding ID, Severity, Vulnerability Type (OWASP mapping), Likely Exploitability (HIGH/MEDIUM/LOW), Quick Remediation (1-2 lines), Suggested Owner (team role), and ETA for fix. Output format: CSV table sorted by Severity then Exploitability then repo. Additional constraint: include one recommended automation rule (Codiga or CI) to prevent recurrence per top-3 recurring findings. Example input: 'repo-a,repo-b' and sample findings JSON.

You are an engineering lead defining style guardrails. Produce a combined set of 12 JavaScript/TypeScript style rules mapped to ESLint configurations and equivalent Codiga patterns. Constraints: include rules for imports, naming, async/await usage, error handling, max function length, and banned globals; each rule must state rationale, a one-line ESLint rule snippet, Codiga rule outline, and a sample violating snippet with a fixed version. Output format: JSON array where each element has keys: id, rationale, eslint, codiga_pattern, bad_example, fix_example. Ensure rules are team-enforceable and low false-positive risk.

You are a senior application-security engineer. Create a Codiga rule pack to detect SQL injection patterns across Java and Node.js backends. Multi-step: 1) provide 3 rules (parameterized query absence, concatenated SQL strings with user input, risky ORM raw queries) with precise detection logic and false-positive mitigations; 2) include 2 short unit test examples per rule (vulnerable and fixed) in code comments; 3) add an automated quick-fix suggestion or secure snippet developers can insert. Output format: YAML rule pack compatible with Codiga, followed by the test examples and quick-fix snippets. Example few-shot: show one vulnerable concat: "query = 'SELECT * FROM users WHERE id=' + req.query.id" and fixed prepared statement.

You are a Security Program Manager designing an enterprise gating policy for Codiga across 100+ repos. Produce a multi-step implementation playbook: 1) severity thresholds by environment (dev/test/stage/prod), 2) onboarding checklist for teams, 3) automated remediation workflow (scan -> create ticket -> assign -> verify) including example GitHub Actions and ticket template, 4) escalation rules and SLAs, 5) metrics dashboard fields to track. Output format: numbered playbook steps with YAML/JSON snippets for CI and a Markdown ticket template. Include rationales and one change-management tip.

Compare Codiga with Snyk, GitHub Copilot, SonarQube. Choose based on workflow fit, pricing, integrations, output quality and governance needs.