claude

noctia

Engineering rules for Claude Code: KISS, modular tested code, security checks, guarded git, and a team of agents (Opus chief, orchestrator and pentester; Sonnet developer; Haiku tester, reader and documenter).

4 on GitHubby Etienne Pouillev0.6.3MITupdated 9 days ago
/

Plugin noctia from marketplace noctia-plugins in EtienneP-26/Noctia. Commands read from the repo's manifest — 7 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (7)

  • audit

    Audit project health (tests, CI, docs, architecture, security, versioning). Use on /audit or when asked what is missing.

  • code-quality

    Noctia code style: KISS, small functions, docstrings, tests. Use when writing, changing or reviewing code.

  • git-workflow

    How to commit and push once git is unlocked. Use before any git add, commit, push or tag.

  • git

    Set how the agent may use git in this project (locked, ask, auto). User-only command.

  • help-me-build-it

    Mentor mode. the agent does not write the build; it guides the user to design, write and debug it themselves. Use when the user runs /help-me-build-it or says they want to learn, do it themselves, or be guided instead of given the solution.

  • release-and-deploy

    Versioning (vX.Y.Z), branches, CI/CD, changelog. Use when setting up or changing releases, deployment or pipelines.

  • security-check

    Security checklist for code changes. Use before finishing a change that touches input, auth, data, network, files or dependencies.

Subagents (7)

  • chief

    The project chief. Main agent of a Noctia session: talks to the user, decides who works on what, never loses the thread. Runs on Opus.

  • developer

    Use to implement one well-defined task of a project: write the code for it, following the project style. Used by /noctia:build.

  • documenter

    Use after a feature is built and tested to write its doc: what was done and how, short by default. Used by /noctia:build.

  • orchestrator

    Use to plan a project or a feature and decide how to build it: features, order, technical choices, git branching. Returns a plan for the chief to show the user. Read-only.

  • pentester

    Use to find the bugs and problems of the project once the features are built (wrong results, crashes, bad edge-case handling, real security flaws in the project's own code). Reports them, never fixes them.

  • reader

    Use to read the codebase when something precise is needed: where a feature lives, where a problem is, how a big codebase fits together, git history, logs, large data files. Cheap and fast, read-only.

  • tester

    Use after a feature is coded: launch the project the normal way, use the feature like a normal user, write and run its tests, and report failures. Does not try to break things. Used by /noctia:build.

Hooks (6)

  • SessionStart

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/session-start.sh"

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-git.sh"

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-secrets.sh"

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/filter-test-output.sh"

  • PostToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/git-mode-from-picker.sh"

  • UserPromptSubmit

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/git-mode-from-prompt.sh"

View source on GitHub

More from EtienneP-26/Noctia

All 2 plugins →

Noctia visual mods for Claude Code: Noctia banner, team panel, agent labels, task checklist and more.

4

Maintain noctia?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins