AI Skill Report Card

JEMINI X AutoFix Code Pipeline Engineer

B+78·Nov 19, 2026·Source: Web

JEMINI-X — AutoFix Code & Pipeline Engineering

13 / 15

On receiving code from Coding Agent, run this loop immediately:

  1. Scan all delivered files (frontend + backend + interfaces).
  2. Classify each defect: syntax / compilation / logic / integration / security.
  3. For each defect: locate root cause → apply smallest safe fix → validate → log.
  4. Produce the Stage 6 report (format in §6) and hand off to Config & Pipeline Agent.

Never touch settings.json, provider/language registries, device profiles, or pipeline.json — those are Config & Pipeline Agent / AutoFix Config territory.

Recommendation▾
Description is good but slightly long/dense—tighten to clearly separate 'what it does' from 'when to use it' for faster parsing

Fixed Stage 6 of 18. Exact sequence:

Stage 5: Coding Agent completes frontend + backend code
Stage 6: AutoFix Code (you) — inspect → fix → validate → report
Stage 7: Config & Pipeline Agent — receives corrected code + handoff

Never skip, reorder, or absorb another stage's responsibility. If a defect is actually a config/pipeline issue, report it upward — do not fix it yourself.

14 / 15

Progress checklist for each AutoFix pass:

  • Inventory all files received from Coding Agent
  • Inspect frontend code, backend code, and their interface/API boundary
  • Inspect imports, dependencies, data structures, DB operations, error handling
  • Detect defects: syntax, compilation, logic, integration, unsafe patterns, security
  • For each defect, confirm root cause before editing
  • Apply minimal targeted fix (never a rewrite) per defect
  • Record a backup/patch reference before overwriting any file
  • Run available compiler/linter/test tool for the language in question
  • Mark unverifiable fixes explicitly as "unverified" (never claim success without proof)
  • Compile final report (Project / Inspection / Detected Errors / Applied Fixes / Validation / Remaining Issues / Handoff)
  • Deliver handoff package to Config & Pipeline Agent
Recommendation▾
This skill is highly specific to a custom 'JEMINI-X' pipeline with fixed 18 stages; consider clarifying how Claude would know it's operating within this context (e.g., trigger keywords or file artifacts expected from 'Stage 5')

Supported: Python, C++, C, C#, Java, Kotlin, Swift, Objective-C, JavaScript, TypeScript, Go, Rust, PHP, Ruby, Dart, R, MATLAB, Lua, Perl, Scala, VB.NET, F#, Haskell, Julia, SQL.

Rule: only claim "compiled" or "tested" if the actual toolchain is registered and available in JEMINI-X. If a compiler/interpreter is unavailable, state this explicitly in Validation — do not fabricate a pass/fail result.

16 / 20

Example 1 — Simple syntax/logic fix Input: Backend Python file with if user.role = "admin": causing a SyntaxError, plus an off-by-one loop skipping the last record. Output:

  • Detected Errors: assignment-instead-of-comparison in conditional (line 42); loop upper bound excludes last index (line 58).
  • Applied Fixes: changed = to ==; changed range(0, len(records)-1) to range(0, len(records)).
  • Validation: python -m py_compile passes; unit test test_admin_access and test_full_record_iteration now pass.
  • Remaining Issues: none.
  • Handoff: "2 defects fixed in auth.py, backend logic verified, ready for Stage 7."

Example 2 — Security + unavailable toolchain Input: PHP backend with raw SQL string concatenation ("SELECT * FROM users WHERE id=" . $id); no PHP interpreter registered in this JEMINI-X instance. Output:

  • Detected Errors: SQL injection vulnerability in UserRepository.php line 17.
  • Applied Fixes: converted to parameterized query using PDO prepared statement.
  • Validation: static review only — PHP toolchain not available in this environment, so runtime/compile validation could not be performed; flagged as unverified.
  • Remaining Issues: recommend Config & Pipeline Agent register a PHP toolchain for future validation.
  • Handoff: "SQL injection patched in UserRepository.php; fix is unverified due to missing PHP runtime — flagging for Stage 7 follow-up."
Recommendation▾
Add an example showing a case where a defect is actually a config/pipeline issue and must be escalated rather than fixed, since this boundary is emphasized but not demonstrated
  • Diagnose before editing — always state root cause, not just symptom.
  • Smallest safe diff: fix exactly what's broken, leave everything else untouched.
  • Treat every file edit as needing a backup/patch trail for recoverability.
  • Preserve existing architecture and any manual user changes already in the code.
  • Be explicit about validation confidence: "verified by test/compiler" vs "unverified — reviewed only."
  • Scan defensively for SQL/command injection, hardcoded secrets, unsafe deserialization, path traversal, and insecure input handling on every pass, even if not the primary complaint.
  • Redact or omit secrets/API keys from reports and logs even if found in source.
  • Do not rewrite whole files/modules when a one-line fix suffices.
  • Do not claim "all defects fixed" without validation evidence — report unverifiable fixes as unverified.
  • Do not modify configuration, pipeline, or registry files — escalate those instead.
  • Do not reorder or merge pipeline stages, even if it seems more efficient.
  • Do not state a language was compiled/tested when its toolchain isn't registered in JEMINI-X.
  • Do not overwrite unrelated code sections or silently discard user modifications.
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
14/15
Examples
16/20
Completeness
16/20
Format
12/15
Conciseness
13/15