agentic-coding-workflow-expert
Expert guide for AI-assisted coding workflows — agentic code generation, multi-agent code swarms, self-healing CI/CD, automated PR review, spec-to-code pipelines, codebase knowledge graphs, and human-in-the-loop approval gates / Panduan ahli untuk workflow pengkodean berbasis AI — generasi kode agentic, code swarm multi-agen, CI/CD self-healing, review PR otomatis, pipeline spec-to-code, knowledge graph codebase, dan gate persetujuan human-in-the-loop.
roedyrustam · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add roedyrustam/vibes-plug --skill agentic-coding-workflow-expertAbout this skill
name: agentic-coding-workflow-expert description: "Expert guide for AI-assisted coding workflows — agentic code generation, multi-agent code swarms, self-healing CI/CD, automated PR review, spec-to-code pipelines, codebase knowledge graphs, and human-in-the-loop approval gates / Panduan ahli untuk workflow pengkodean berbasis AI — generasi kode agentic, code swarm multi-agen, CI/CD self-healing, review PR otomatis, pipeline spec-to-code, knowledge graph codebase, dan gate persetujuan human-in-the-loop." author: "vibes-plug-swarm"
version: "3.0.0"
Agentic Coding Workflow Expert
1. Agentic Code Generation Patterns / Pola Generasi Kode Agentic
Implement autonomous code generation workflows. Implementasikan workflow pembuatan kode otonom.
Core Patterns / Pola Inti:
- Single-file vs Multi-file Generation:
- Single-file: Isolate scope, update specific modules.
- Multi-file: Coordinate state across files, ensure API contract consistency.
- Context-Aware Completion: Query codebase knowledge graph for semantic context before generating.
- Ghost Text / Inline Suggestion: Provide real-time snippet integration paths.
- Plan → Implement → Verify → Refine: Always loop through planning, writing, testing, and iterating.
Code Example: Multi-file Generation Workflow
// workflow-generator.ts
interface GenerationTask {
plan: string;
files: string[];
}
class AgenticGenerator {
async execute(task: GenerationTask) {
console.log(`[PLAN] Executing: ${task.plan}`);
const generatedFiles = await this.generateFiles(task.files);
for (const file of generatedFiles) {
const isValid = await this.verify(file);
if (!isValid) {
await this.refine(file);
}
}
}
private async generateFiles(files: string[]) {
// Generate code with multi-file context awareness
return files.map(f => ({ name: f, content: "// generated code" }));
}
private async verify(file: any) {
// Run linter and tests
return true;
}
private async refine(file: any) {
// Apply fixes based on verification failures
}
}
2. Multi-Agent Code Swarms / Swarm Kode Multi-Agen
Coordinate multiple specialized agents for complex engineering tasks. Koordinasikan beberapa agen khusus untuk tugas rekayasa yang kompleks.
Swarm Architecture:
- Fan-out: Dispatch tasks to Frontend Agent, Backend Agent, Test Agent, and Review Agent.
- Shared Workspace: Utilize branched git worktrees for isolated, parallel development.
- Director Agent: Resolve conflicts, validate coherence across boundaries, merge branches.
Code Example: TypeScript Swarm Orchestration
// swarm-orchestrator.ts
enum AgentRole {
FRONTEND, BACKEND, TEST, REVIEW, DIRECTOR
}
class SwarmDirector {
async orchestrate(featureSpec: string) {
// Fan-out
const feTask = this.dispatch(AgentRole.FRONTEND, featureSpec);
const beTask = this.dispatch(AgentRole.BACKEND, featureSpec);
await Promise.all([feTask, beTask]);
// Testing and Review
const testResults = await this.dispatch(AgentRole.TEST, "Run integration tests");
const reviewStatus = await this.dispatch(AgentRole.REVIEW, "Review cross-boundary changes");
if (reviewStatus.approved) {
await this.mergeWorktrees();
} else {
await this.resolveConflicts();
}
}
private async dispatch(role: AgentRole, context: string) {
// Send task to specific agent queue
return { approved: true };
}
private async mergeWorktrees() {}
private async resolveConflicts() {}
}
3. Spec-to-Code Pipeline / Pipeline Spec-to-Code
Transform natural language specifications into tested implementation. Ubah spesifikasi bahasa alami menjadi implementasi yang teruji.
Pipeline Steps:
- PRD to Test Cases (TDD): Extract acceptance criteria, generate unit/integration tests first.
- Implementation: Write code to satisfy generated tests.
- Validation: Run tests, enforce coverage thresholds.
Code Example: Spec-to-Test-to-Code
# spec_pipeline.py
def run_spec_to_code(prd_text: str):
# 1. Extract and Generate Tests
criteria = extract_acceptance_criteria(prd_text)
tests = generate_tests_from_criteria(criteria)
# 2. Implement
implementation = generate_code_to_pass(tests)
# 3. Validate
result = run_tests(implementation, tests)
if not result.passed:
implementation = refine_code(implementation, result.errors)
return implementation
def extract_acceptance_criteria(text): return []
def generate_tests_from_criteria(criteria): return []
def generate_code_to_pass(tests): return ""
def run_tests(code, tests): return type('Result', (), {'passed': True, 'errors': []})
def refine_code(code, errors): return code
4. Self-Healing CI/CD Pipelines / Pipeline CI/CD Self-Healing
Automate failure recovery in integration pipelines. Otomatisasi pemulihan kegagalan dalam pipeline integrasi.
Capabilities:
- Detection: Parse terminal output and stack traces from CI runners.
- Root-Cause Analysis: Pattern match common failure modes (e.g., missing dependencies, type errors).
- Auto-Fix Generation: Propose fixes with confidence scoring.
- Rollback Safety: Always create a fix branch; never push directly to
main.
Code Example: CI Failure Analyzer
#!/bin/bash
# ci-self-heal.sh
LOG_FILE="ci-output.log"
FAIL_PATTERN="ERR!"
if grep -q "$FAIL_PATTERN" "$LOG_FILE"; then
echo "[CI] Failure detected. Triggering self-healing agent..."
# Analyze logs and generate patch
PATCH_FILE=$(agent-analyze-ci --log "$LOG_FILE")
if [ -n "$PATCH_FILE" ]; then
git checkout -b auto-fix-$(date +%s)
git apply "$PATCH_FILE"
git commit -m "chore(ci)
Read the complete source ↗