g-bastianelli
- 46 skills
- 0 followers
- 17 hours ago last updated
- ▌ Audit · g-bastianelliScan all skills, agents, personas, and banner prompts in this nuthouse repo against the _templates/ source of truth. Reports missing
- ▌ Pr · g-bastianelli bundleUse automatically when the user asks to create, open, draft, or publish a GitHub PR, pull request, review request, "ouvre une PR", "fais la PR", "crée une pull request", or says the branch is ready for review. Drafts from branch history and, after confirmation, publishes the branch before creating the PR. Do not use for commits, plain git status, diff, log, push-only, rebase, or non-GitHub merge requests.
- ▌
- ▌ Release · g-bastianelliUse when releasing nuthouse plugin changes to Claude Code and Codex users — "release", "ship la release", "publie les plugins", "bump les versions", or after merging a plugin-touching PR. Detects changed plugins via the marketplace sha pins, bumps plugin versions BEFORE sha pins, verifies both runtime manifests and registries, reports both refresh paths, and hands each commit to git-gremlin:commit. Two auto-detected phases: versions (pre-merge, on the feature branch) and shas (post-merge, on main).
- ▌ Scope · g-bastianelliInspect branch and working-tree changes in a configured moon monorepo and report the affected projects. Use for cross-project work or before broad checks; do not invoke merely because a task starts.
- ▌ Verify · g-bastianelliRun moon typecheck, lint, and test tasks for affected projects after edits. Use only in a configured moon workspace; report fresh command evidence without adding review or handoff ceremony.
- ▌
- ▌ Commit · g-bastianelli bundleUse automatically when the user asks to commit changes, create a commit, write a commit message, commit staged changes, commit everything, run git commit, "fais le commit", "commit mes changements", or "crée un commit". Commits an existing staged selection, or stages dirty changes automatically for an actual commit while preserving explicit file scope. Do not use for plain git status, diff, log, push, rebase, or PR creation.
- ▌ Plan · g-bastianelliUse when planning implementation for a Linear issue after greet or from an issue id. Grounds an issue-scoped plan in source and code, reviews behavior and verification in proportion to risk, then prepares the authorized implementation handoff. Does not implement or silently change source Acceptance.
- ▌ Research · g-bastianelliUse automatically when the user wants a researched, fact-checked, or cited answer from the web — "fais une recherche", "creuse le sujet", "vérifie cette info", "trouve-moi des sources sur", "research X", "fact-check X", "find sources on X", "dig into X", or any question whose answer needs several cross-checked web sources. Prefer this over a bare WebSearch whenever the answer should be sourced rather than answered from memory. Fan-out web search → fetch + summarize → adversarial verification → cited synthesis. Zero parametric knowledge — answers only from verified sources.
- ▌ Stop · g-bastianelliUse when the user wants to stop future Monkey Maestro dispatches for a Linear project. Appends one approved active:false control while leaving existing Superset work untouched.
- ▌
- ▌ Greet · g-bastianelliUse only at fresh session start when an issue identifier comes from the current branch or first user prompt and no issue context is already available. Never retrigger from resume, compaction, or a conversation summary. Fetches a sourced brief, resolves spec/project-plan authority, and hands authorized delivery to plan. Never implements.
- ▌ Spawn · g-bastianelliUse when the user explicitly wants either one Linear-authorized issue launched or recovered in a task-linked Superset workspace, or one free-form quick fix launched in a branch-bound workspace.
- ▌ Start · g-bastianelliUse when the user wants to activate Monkey Maestro for a Linear project. Resolves ordinary local Superset transport, writes one minimal control after one approval, and enters orchestration.
- ▌ Review Skills · g-bastianelliUse when the user wants to review the quality of existing nuthouse skills — runs a structural audit then queues selected skills for testing and description optimization via skill-creator. Use when the user says "are my skills good?", "review all skills", "check my skills", "audit quality".
- ▌ Status · g-bastianelliUse automatically when the user supplies a Linear project URL or asks to inspect one project's Maestro state. Reports the current control, live Linear frontier, and available capacity without inspecting Superset.
- ▌ Form Rules · g-bastianelliForm discipline for TypeScript — the schema is the only converter, input and output are different types, a required field is seeded blank not absent, submit is never gated on validity, and each failure names itself.
- ▌ Validation · g-bastianelliValidation discipline for TypeScript — one schema source of truth, parse data once at each trust boundary, and derive static types from schemas. Applies whenever editing or creating TypeScript files.
- ▌ Scaffold Agent · g-bastianelliUse when adding a new dedicated subagent to an existing plugin in this `nuthouse` marketplace. Asks for parent plugin, agent name (descriptive role, no vague names like "agent" / "helper"), description, model (`haiku` for parsing/fetch+summary vs default for reasoning), explicit tools allowlist, input format spec, output format spec (SDD vs structured report vs custom). Generates `<plugin>/agents/<name>.md` with the right frontmatter (name, description, model, tools list) and the standard Mission / Input / Output / Hard rules sections. Encodes the subagent and SDD conventions from the legacy CLAUDE.md.
- ▌
- ▌ React Rules · g-bastianelliReact implementation discipline — one component per file, folders mirror JSX ownership, children receive stable IDs/primitives, state lives at the highest durable layer, and styling ownership stays explicit.
- ▌ Type Safety · g-bastianelliType-safety discipline for all TypeScript work — prove unknown values, avoid any/as/non-null assertions, prefer inference and exhaustive unions. Applies whenever editing or creating TypeScript files.
- ▌
- ▌ Audit Spec · g-bastianelliReview an existing spec for contradictory behavior, unverifiable acceptance, unsupported decisions, and repository conflicts. Returns concrete blockers and a readiness verdict; use before ratification or when a spec's quality is in doubt.
- ▌ Write Plan · g-bastianelliTurn an approved spec into an implementation plan grounded in repository code, with dependency-ordered deliverables, necessary contracts, and observable acceptance checks. Use before implementing a ratified Acid Prophet spec.
- ▌ Write Spec · g-bastianelliTurn a feature or project request into a codebase-grounded spec with observable acceptance criteria and an independent audit. Use when a written spec is wanted before planning or Linear issue breakdown.
- ▌ Debug Local · g-bastianelliUse when the user reports a runtime error, a service not starting, an auth/OIDC failure, or missing env vars in local dev on the notom platform. Investigate proactively with available tools before asking the user to run anything.
- ▌ Check Drift · g-bastianelliUse during issue planning or on a feature branch before/during PR creation to detect drift against the authoritative SDD Acceptance and constraints. Planned-intent mode writes a local drift report; branch mode can optionally post it as a PR comment.
- ▌ Reconcile · g-bastianelliUse when the user explicitly asks Monkey Maestro to inspect Superset transport for a project. Produces an optional read-only issue/runtime correlation report and never repairs or gates scheduling.
- ▌ Hono Pipeline · g-bastianelliImplementation discipline for Hono with a typed RPC/contract stack — discover local conventions, then move contract → resource error → pure service Result → exhaustive unwrap → thin router → wiring.
- ▌ State Machine · g-bastianelliState-machine discipline for TypeScript lifecycle, workflow, reducer, and state-machine files — make illegal states unrepresentable, keep transitions pure and exhaustive, and design for replay and concurrency.
- ▌ Next Issue · g-bastianelliUse when a Linear issue is finished and the user wants the next issue, or asks which issue to take next in the project. Reads current statuses and blockers, distinguishes active work from available work, and recommends a startable issue without changing Linear.
- ▌ Sync Insomnia · g-bastianelliUse when adding, modifying, or removing API endpoints and the corresponding Insomnia collection needs to be updated. Edits the Git-Synced YAML collection directly, commits, and tells the user to Pull in Insomnia.
- ▌ Result Pattern · g-bastianelliResult/error discipline for backend domain and service code — expected outcomes return Result variants, infrastructure failures stay exceptional, and one exhaustive unwrap translates at the transport edge.
- ▌ Orchestrate · g-bastianelliUse when the user wants Monkey Maestro to run an active Linear project. Counts live started issues, fills remaining slots, and safely creates or reuses one Superset workspace per selected issue.
- ▌ Drive Scaleway · g-bastianelliUse when working with any Scaleway resource — IAM, instances, databases, registry, observability, networking. Drives the `scw` CLI directly to inspect and modify resources instead of suggesting manual console actions.
- ▌ Create Issue · g-bastianelliUse to add one coherent Linear issue to an existing project. Reuses supplied context, drafts exact Acceptance and observable verification, resolves consequential questions, and creates the complete authorized payload. Also prepares read-only corrections for existing issues. Use create-project to resume a project cascade.
- ▌ Write Checklist · g-bastianelliUse during issue planning or when a feature approaches QA/PR review to derive a per-spec acceptance checklist. It preserves source AC ids, writes an open checklist, and never treats checklist generation as human feature acceptance.
- ▌ Observe Platform · g-bastianelliUse when investigating a service issue, checking logs, querying metrics, or verifying the health of any notom-platform resource on Scaleway staging or prod. Queries Loki logs and Prometheus metrics directly via the cockpit API — never punts to Grafana.
- ▌ Code Organisation · g-bastianelliCode-organisation discipline for TypeScript — named exports, declarative entry points, one responsibility per file, explicit package boundaries, and reuse before writing. Applies whenever editing or creating TypeScript files.
- ▌ Create Project · g-bastianelliUse to create a Linear project with complete issue bodies, meaningful milestones, and justified dependencies from a spec, Acid Prophet artifact set, or product interview. Also reviews existing projects with a read-only correction preview. Reviews the full proposal before authorized writes, verifies the resulting graph, and resumes partial creation by exact markers.
- ▌ Testing Discipline · g-bastianelliTesting discipline for TypeScript test files — reproduce regressions first, test observable behavior and typed failures, keep doubles at owned boundaries, and preserve unexpected rejections.
- ▌ Write Constitution · g-bastianelliUse when a project needs immutable governing principles that every spec / audit / drift check is held against — runs a one-question-at-a-time interview to extract project-specific articles (test-first, anti-abstraction, library boundaries, etc.), writes them to docs/acid-prophet/constitution.md, and commits. The spec-auditor reads this file on every audit and treats each article as an extra gate.
- ▌ Create Milestone · g-bastianelliUse to add one milestone to an existing Linear project. Defines a meaningful delivery boundary and exit evidence, reuses supplied context, and creates the complete authorized milestone. Use create-project for cascade creation or recovery.
- ▌ Handle Review Comments · g-bastianelliUse whenever an agent is handling GitHub pull-request review comments, whether it fixes them or dismisses them. Let the agent assess and address them autonomously; this skill adds only two invariants—a reply announcing a fix must not precede the push of that fix, and any comment the agent dismisses must receive an explanatory reply and then be resolved.