craft

Implement features, review code, refactor, and debug failing tests.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LeoCode03/spkie_gpu --skill craft-leocode03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: craft
Source: https://github.com/LeoCode03/spkie_gpu/tree/main/.claude/skills/craft
Command: npx skills add https://github.com/LeoCode03/spkie_gpu --skill craft-leocode03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables rapid translation of abstract tasks into production-quality code for ad-hoc work outside the standard integration lifecycle. It helps teams implement new features, review existing code for violations or bugs, refactor towards compliance, or debug failing tests without waiting for CR lanes.

Core Features & Use Cases

  • Ad-hoc implementation: translate user task statements into production-grade code that follows project conventions.
  • Code review & compliance: identify violations, security issues, and debt in existing code and propose fixes.
  • Refactor and debugging: rework code to restore compliance and fix failing tests with minimal disruption.
  • Context-driven execution: loads bundled references before acting to apply platform and architecture rules.

Quick Start

Describe the task and desired outcome, and Craft will load bundled references and begin generating production-ready code.

Frequently Asked Questions about craft

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

FAQPage Schema
How do I implement production-grade code for ad-hoc tasks outside the CR pipeline?

To implement production-grade code for ad-hoc tasks, describe the task and desired outcome. The tool loads bundled references and project patterns to generate compliant code outside the CR pipeline.

Can I review existing code for violations and security issues without a CR lane?

Yes, you can review existing code for violations and security issues without a CR lane. The tool identifies compliance debt and proposes targeted fixes based on loaded project conventions.

What is the best way to refactor non-compliant code and debug failing tests in non-CR contexts?

The best way to refactor non-compliant code and debug failing tests is using the bundled /triage and /build workflows. These workflows rework code to restore compliance and fix tests with minimal disruption.

Does this ad-hoc coding approach require specific project patterns to follow conventions?

Yes, this ad-hoc coding approach requires specific project patterns. It relies on bundled references and loaded context to apply platform and architecture rules, ensuring generated code matches existing conventions.