agentsclimarketplace

Software quality workflows

Skill S3YED/appie-kit/skills/software-development/software-quality-workflows

Build Your Own AI Employee. The complete starter kit for OpenClaw + Hermes Agent. 155 deduplicated skills, drag-and-drop workspace, case studies, install scripts.

Install
npx -y skills add S3YED/appie-kit --skill software-quality-workflows

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.

SKILL.md

2.2 KB, 440 tokens by cl100k_base, as published. Nobody here has run it

Software Quality Workflows

Use this umbrella for implementation-quality loops: test-first work, systematic debugging, short spikes, simplification passes, debugger sessions, and pre-commit review.

Pick the mode

SituationMode
New behavior or bug fix with clear expected outputTDD: RED → GREEN → REFACTOR.
Unknown root causeSystematic debugging: reproduce, localize, hypothesize, fix, verify.
Uncertain approach or APISpike: time-boxed throwaway experiment before production changes.
Recent change is too complexSimplify-code: parallel or focused cleanup with behavior preserved.
Ready to hand off/commitRequesting code review: security scan, quality gates, auto-fix only when safe.
Runtime behavior is opaqueDebugger-assisted investigation via pdb/debugpy or Node inspector.

TDD loop

  1. Write or identify a failing test that captures the requirement.
  2. Run only the relevant test to see RED.
  3. Implement the smallest fix.
  4. Run focused then broader tests.
  5. Refactor while tests stay GREEN.

Systematic debugging loop

  1. Reproduce with exact command/input.
  2. Observe logs, state, failing assertions, and environment.
  3. Narrow the fault with instrumentation or debugger probes.
  4. Fix the root cause, not the symptom.
  5. Verify the original failure and a regression test.

Spikes

Create disposable experiments under a clearly temporary path. Do not mix spike code into production without reimplementation or review. End with a decision: adopt, reject, or investigate further.

Simplification and review

Before committing, inspect diff shape, remove incidental complexity, check security-sensitive paths, and run project gates. If using subagents for cleanup/review, independently verify their claims.

Debugger notes

  • Python: use pdb for local stepping and debugpy when a DAP/remote attach flow is needed.
  • Node: start with node --inspect/--inspect-brk and inspect through Chrome DevTools Protocol when logs are insufficient.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.