software-engineering

Guide coding changes through testing, debugging, refactoring, and review evidence.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill software-engineering-jcetools-petra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-engineering
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/software-engineering
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill software-engineering-jcetools-petra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers follow reliable software engineering practices so changes are implemented correctly, validated with tests, and verified through review and debugging evidence instead of guesswork.

Core Features & Use Cases

  • Testing-first bug fixes: Convert failures into deterministic, scenario-named test cases using TDD so regressions are prevented.
  • Debugging and verification workflow: Apply a systematic investigation loop (read, reproduce, isolate, trace, fix, verify) to reach root cause.
  • Refactoring and code review discipline: Enforce refactoring boundaries, concurrency-safe patterns, and review automation gates to maintain quality during iteration.
  • Practical use cases: Fixing production bugs, refactoring risky modules, adding CI-quality checks, and validating end-to-end flows (e.g., with Playwright) for confidence.

Quick Start

Ask your agent to help you debug a failing test, propose a minimal fix, and add a deterministic regression test to verify the solution.

Frequently Asked Questions about software-engineering

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

FAQPage Schema
How do I fix a bug using TDD to prevent future regressions?

Debug systematically by reading code, reproducing the failure, isolating the trigger, tracing execution, applying a fix, and verifying the resolution. This investigation loop ensures you reach the actual root cause rather than patching symptoms blindly.

How do I debug a failing test to find the root cause?

Debug systematically by reading code, reproducing the failure, isolating the trigger, tracing execution, applying a fix, and verifying the resolution. This investigation loop ensures you reach the actual root cause rather than patching symptoms blindly.

What is the best way to refactor risky modules while maintaining quality?

Validate end-to-end application flows using E2E validation tools like Playwright to gain deployment confidence. This systematic verification requires deterministic tests and passing typecheck and lint runs before reporting task completion.

How do I validate end-to-end flows before shipping code changes?

Validate end-to-end application flows using E2E validation tools like Playwright to gain deployment confidence. This systematic verification requires deterministic tests and passing typecheck and lint runs before reporting task completion.

Does this software engineering workflow support concurrency-safe logic implementation?

Yes, it applies concurrency-safe patterns during feature implementation and refactoring. It enforces concurrency-safe logic boundaries and requires verification through passing test, typecheck, and lint runs before any coding changes are reported as complete.