apply

Implement tasks from change artifacts using Serena framework semantic tools.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill apply-minhquan2904
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/apply
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill apply-minhquan2904

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement tasks from change artifacts using Serena framework's semantic tools, with project standards enforcement and Feature Profile cross-checking.

Core Features & Use Cases

  • Semantic code navigation and automated editing using Serena MCP tools to locate, modify, and validate changes.
  • Enforces project standards by loading required skills, rules, and conventions before code generation.
  • Automates end-to-end change implementation from design/specs to generated source files with task tracking.

Quick Start

Provide the change name and run the apply workflow to generate compliant source code from your change artifacts.

Frequently Asked Questions about apply

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code generation from change artifacts while enforcing project standards?

Automating code generation from change artifacts involves loading project conventions and required rules before using semantic tools to interpret specs and generate production-ready source code. This ensures automated changes adhere to established project standards.

What is semantic editing for source code and how does it work?

Semantic editing uses framework tools to navigate, locate, and modify source code based on its structural meaning rather than plain text matching. It validates changes against project rules to drive compliant code creation.

How do I implement change tasks using Serena framework tools?

Implementing change tasks with Serena framework tools requires an onboarding workflow that loads memory, validates skills, and interprets specifications. It uses semantic navigation to locate and modify code, updating task status throughout the process.

Do I need predefined change artifacts to use automated semantic code generation?

Yes, predefined change artifacts are required to use automated semantic code generation. The workflow interprets these specific design specifications and feature profiles to drive source file creation and ensure alignment with project conventions.

What is the best way to ensure generated source code aligns with existing project conventions?

Ensuring generated source code aligns with project conventions requires strictly enforcing mandatory protocol steps, including memory-based convention loading and design alignment cross-checking before semantic code editing and file creation begins.