Skip to main content
Run any Skill in Manus
with one click
AllanWessels
GitHub creator profile

AllanWessels

Repository-level view of 20 collected skills across 1 GitHub repositories.

skills collected
20
repositories
1
updated
2026-05-25
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

agent-model-selection
software-developers

Pass model explicitly when dispatching sub-agents. Parent-default inheritance bypasses cost considerations; reserve stronger models for tasks that genuinely need them.

2026-05-25
api-rewrite-sweep
software-developers

When a commit changes a component's public API, the same commit must update every test asserting the removed surface — split commits leave CI broken even when each commit is internally consistent.

2026-05-25
audit-then-fanout-fix
software-developers

When a class of bug keeps slipping through tests, run a coverage-matrix audit first, then fan out fix agents per gap — don't whack-a-mole individual failures.

2026-05-25
ci-vs-dev-environment-parity
software-developers

Before pushing to CI, validate that your local test run is representative — three predictable axes diverge (gitignored fixtures, dev-only ports, dev-only env vars) and each has a deterministic fix.

2026-05-25
fix-first-then-test
software-developers

Land every code fix before running the test harness. Use grep + read to debug; the harness is a verifier, not a debugger.

2026-05-25
observable-outcome-tests-over-mocks
software-quality-assurance-analysts-and-testers

Tests that mock the layer where the bug lives cannot catch bugs at that layer. Write tests that drive the same code path the user drives, ending at something the user can see.

2026-05-25
parallel-fanout-verification
software-developers

When verifying or fixing a multi-layer change, dispatch each test layer and each independent fix as a parallel sub-agent rather than running serially in the main context.

2026-05-25
pre-handoff-clean-state-proof
software-developers

Before saying "ready, retest", prove the state is clean by running a concrete numbered checklist. Never claim clean state — demonstrate it with real command output.

2026-05-25
Showing top 8 of 20 collected skills in this repository.
Showing 1 of 1 repositories
All repositories loaded