poteto/noodle

reflect

Reflect on the conversation and update the brain.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/poteto/noodle --skill reflect

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Reflect

Review the conversation and persist learnings — to brain/, to skill files, or as structural enforcement.

Process

Use Tasks to track progress (TaskCreate per step, TaskUpdate to in_progress/completed).

  1. Read `brain/index.md` to understand what notes already exist
  2. Scan the conversation for:
  • Mistakes made and corrections received
  • User preferences and workflow patterns
  • Codebase knowledge gained (architecture, gotchas, patterns)
  • Tool/library quirks discovered
  • Decisions made and their rationale
  • Friction in skill execution, orchestration, or delegation
  • Repeated manual steps that could be automated or encoded
  1. Skip anything trivial or already captured in existing brain files
  2. Route each learning to the right destination (see Routing below)
  3. Update `brain/index.md` if any brain files were added or removed

Routing

Not everything belongs in the brain. Route each learning to where it will have the most impact.

Structural enforcement check

Before routing a learning to brain/, ask: can this be a lint rule, script, metadata flag, or runtime check? If yes, encode it structurally and skip the brain note. See brain/principles/encode-lessons-in-structure.md.

Brain files (brain/)

Codebase knowledge, delegation principles, gotchas — anything that informs future sessions. This is the default destination. Use the brain skill for writing conventions.

  • One topic per file. File name = topic slug.
  • Group in directories with index files using [[wikilinks]].
  • No inlined content in index files.

Skill improvements (.agents/skills/<skill>/)

If a learning is about how a specific skill works — its process, prompts, or edge cases — update the skill directly. Use the skill-creator skill for guidelines on effective skill content.

Orchestration workflow improvements

If the session revealed systemic orchestration issues, route to:

  • Brain principle (new delegation heuristic) → brain/delegation/
  • Skill mechanics change (monitoring loop, review step) → relevant skill file
  • New skill opportunity (recurring workflow that could be encoded) → note in summary for the user

Backlog items (brain/todos.md)

Follow-up work that can't be done during reflection — bugs, non-trivial rewrites, tooling gaps. Use the todo skill to file.

Summary

## Reflect Summary
- Brain: [files created/updated, one-line each]
- Skills: [skill files modified, one-line each]
- Structural: [rules/scripts/checks added]
- Todos: [follow-up items filed]
du même dépôt

Autres Skills

Tous les Skills
poteto
Communauté

debugging

Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".

Installations / 1h
1
GitHub Stars
646
Mis à jour
19 mars
poteto
Communauté

unslop

Remove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: "unslop", "humanize", "make this sound human", "clean up this writing", "edit for voice", "de-AI this text".

Installations / 1h
1
GitHub Stars
646
Mis à jour
19 mars
poteto
Communauté

adversarial-review

Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".

Installations / 1h
1
GitHub Stars
613
Mis à jour
19 mars
poteto
Communauté

brain

Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.

Installations / 1h
1
GitHub Stars
613
Mis à jour
19 mars