kostiantyn-matsebora
UserAn AI software engineering team that behaves like a real one. Drops into your project, self-onboards, and gets to work.
Categories
Indexed Skills (11)
ginee-address-review
Address code-review remarks on an open PR. Ingests `pulls/{N}/comments` + `/reviews`, routes per role, surfaces a consolidated plan table for user approval (no exception), then reconciles fix-track patches into one cycle commit + posts per-thread replies + one sticky cycle summary. Idempotent. Use when user says 'address review on PR
ginee-file-bug
File a bug report against the primary GitHub repo (the adopter's own project) via the ginee framework's GitHub-integration workflow. Use when the user asks to 'file a bug', 'report a bug', 'create a bug issue' for the current project. Drafts a structured issue using core/templates/issues/bug-report.md, surfaces the draft for approval, then creates a labelled GitHub issue.
ginee-file-framework-bug
File a bug report against the ginee framework upstream repo (NOT the adopter's own project) via the framework's outbound-issue workflow. Use when the user asks to 'file a framework bug', 'report a framework issue', 'file an issue against ginee itself'. Drafts a structured issue using core/templates/issues/framework-bug-report.md and targets github.framework-repo.
ginee-file-framework-feature
File a feature request against the ginee framework upstream repo (NOT the adopter's own project) via the framework's outbound-issue workflow. Use when the user asks to 'file a framework feature', 'request a framework feature', 'propose a change to ginee itself'. Drafts a structured issue using core/templates/issues/framework-feature-request.md and targets github.framework-repo.
ginee-pick-up
Pick up a task from any source and run it through the ginee Phase 1–8 lifecycle. Task source can be a GitHub issue (`#N`), a TODO line in any TODO file (root or nested), or a freeform description. Use when the user asks to 'pick up
ginee-promote-discussion
Promote a GitHub discussion to a labelled issue via the ginee framework. Use when the user asks to 'promote discussion
ginee-reindex
Reconcile local/index/ with the current repo state at the named scope per the ginee index protocol. Three sweeps — SHA drift on existing entries, new files within existing class globs, stale entries (prompt). Use when the user asks to 'reindex', 'reindex <file>', 'reindex <class>', 'reconcile the index', 'refresh the index', or when SHA-256 drift is detected pre-dispatch.
ginee-triage
List ready work across all task sources (GitHub issues + TODO files) and propose a pickup order. Use when the user asks to 'triage', 'list ready work', 'what should I work on', 'show the backlog'. Optional positional arg narrows scope ('issues' / 'framework' / 'todos'). Returns a merged table; never picks on its own.
ginee-discovery
Run the ginee framework's initial discovery on this project. Use when starting a new framework install, when local/project-profile.md is missing, or when the user asks to 'run initial discovery', 'discover the project', 'set up ginee'. Detects stack, paths, doc artefacts, SDLC tooling; writes local/project-profile.md + local/bindings.md + local/framework.config.yaml; dispatches ai-engineer to populate local/index/manifest.yaml.
ginee-file-feature
File a feature request against the primary GitHub repo (the adopter's own project) via the ginee framework's GitHub-integration workflow. Use when the user asks to 'file a feature', 'request a feature', 'create a feature request' for the current project. Drafts a structured issue using core/templates/issues/feature-request.md, surfaces the draft for approval, then creates a labelled GitHub issue.
ginee-rediscover
Run full re-discovery of the project via the ginee framework. Use when the user asks to 'rediscover', 'refresh project discovery', 're-run discovery', or when major project structure has changed since the last discovery. Re-detects everything and overwrites local/* artefacts; preserves local/roles/ (project-authored).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.