Skip to main content
Run any Skill in Manus
with one click
GitHub repository

nebu

nebu contains 10 collected skills from innoq, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
10
Stars
4
updated
2026-05-12
Forks
0
Occupation coverage
3 occupation categories · 100% classified
repository explorer

Skills in this repository

nebu-agent-oracle
software-developers

Matrix Client-Server API spec expert with Nebu project memory. Use when asking about Matrix events, endpoints, or spec rules; requesting compliance review of a Matrix feature; or when the nebu-pipeline needs spec guidance during a dev or review step.

2026-05-12
nebu-pipeline-epic
software-developers

Runs a full epic by iterating through stories, each in a fully isolated story pipeline sub-agent. Use when you want to implement all pending stories of an epic without manual step-by-step control.

2026-05-12
nebu-pipeline
software-developers

Orchestrates the full Nebu dev lifecycle with TDD-first order, dev↔review cycles, conditional security and UX gates, and full resume capability via pipeline-state.yaml. Use --resume, --from <step>, or --bug.

2026-05-12
nebu-agent-testing
software-quality-assurance-analysts-and-testers

CI engineer for the Nebu project. Runs the full test suite against a fresh stack, manages GitLab CI config, and reports actionable bug lists. Called by nebu-pipeline at the CI gate; also usable directly for ad-hoc runs and CI config work.

2026-05-12
bmad-maintain-arc42
software-developers

Delta-Update for arc42 docs — reads docs/.arc42-manifest.json to determine which planning artifacts changed since the last generation, then regenerates only the affected arc42 sections and updates the manifest per-section. Use when you want a fast, targeted refresh instead of a full /bmad-generate-arc42 run.

2026-05-12
bmad-pipeline
software-developers

Orchestriert den kompletten BMAD-Entwicklungszyklus als automatische Pipeline: bmad-create-story → bmad-testarch-atdd → bmad-dev-story → CI-Pipeline-Gate (build, unit-go, unit-elixir, playwright-e2e, integration) → bmad-testarch-test-review → bmad-code-review → bmad-security-review (Kassandra, conditional) → bmad-maintain-arc42, jeweils in frischem Kontext. CI-Gate blockiert den Review bei Fehlern. E2E-Tests müssen bei jeder UI-Story wachsen. Arc42 wird nach jeder Story delta-aktualisiert. Der Code-Review-Skill fixt Minor Issues selbst ("fixe minor issues instantly"). Pausiert nur bei Major/Critical Issues (User-Entscheidung), am Epic-Ende zwingend mit Kassandra-Security-Review und danach für die Retrospektive (liest sprint-status.yaml). Trigger: "bmad pipeline", "bmad run", "bmad start", "story pipeline", "neues feature", "story durchlaufen", "pipeline starten", immer wenn der User den kompletten BMAD-Flow starten will ohne jeden Schritt einzeln aufzurufen.

2026-05-12
nebu-agent-kassandra
information-security-analysts

Adversarial security reviewer for the Nebu project. Named after the Trojan prophet who was always right and never believed. Finds what others miss — CRITICAL/HIGH findings block the commit. Called by nebu-pipeline on security_review:required stories and epic-end; also usable directly for ad-hoc reviews.

2026-05-12
nebu-agent-ux
software-developers

Admin UI specialist for the Nebu project. Designs, implements, and tests the Admin UI (Go Templates + Tailwind + DaisyUI). Accessibility requirements from the PRD are hard constraints, not guidelines. Automatically called by nebu-pipeline when a story has ui:true; also usable directly for design reviews, UI story planning, and Playwright test work.

2026-05-12
nebu-setup
software-developers

Sets up Nebu Dev module in a project. Use when the user requests to 'install nebu module', 'configure Nebu Dev', or 'setup nebu pipeline'.

2026-05-12
bmad-pipeline-local
software-developers

BMAD-Pipeline optimiert für lokale LLMs (256k Kontextfenster, kein Task-Tool). Läuft vollständig im Haupt-Kontext ohne Subagenten. Nutzt RTK intensiv für alle Datei-, Git- und Suchoperationen (60–90% Token-Einsparung). Strukturiert jede Phase mit expliziten Kontext-Checkpoints und aggressiver Kompression. Kein Modell-Routing — das lokale Modell übernimmt alle Gates. Trigger: "pipeline local", "lokale pipeline", "offline pipeline", "ollama pipeline", "pipeline ohne api", "bmad local run", immer wenn der User die BMAD-Pipeline ohne Cloud-API starten will.

2026-05-03