hellotern

hellotern/Sextant

Plugin Claude Code

Plugin marketplace listing 1 plugin: sextant.

hellotern/Sextant

Plugin Claude Code

Architecture-aware engineering principles framework for Claude Code. Provides systematic, tiered workflows for bug fixes, new features, refactoring, code review, test writing, requirements refinement, debugging, shipping, sprint planning, migrations, and security audits.

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before writing any code for a new feature, module, class, or API endpoint. Use when the thing being built does not yet exist in the codebase — adding net-new functionality. Stronger signals: "add", "implement", "create", "build", "new feature", "new endpoint", explicit new requirement. Use…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before reading any code or proposing any fix when the bug location is unknown. Use when you have a symptom (error, crash, unexpected output) but cannot yet point to the specific function or line where it originates. Stronger signals: "I don't know where this is coming from", "can't reproduce…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before writing any fix or editing any code to address a bug. Use when the code should do X but currently does Y — restoring correct behavior in existing code. Stronger signals: error messages, stack traces, "not working", "broken", "failing", "regression", "it used to work". Use sextant:debug…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before starting any cross-module migration, upgrade, or technology conversion. Use when multiple files or modules must change in a coordinated sequence — framework upgrades, language conversions, schema migrations, or major API version changes. Stronger signals: "migrate", "upgrade", "convert"…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before changing, enhancing, or refactoring any existing functionality. Use when the code already exists and you are altering its behavior, performance, or structure — not fixing a bug. Stronger signals: "modify", "refactor", "optimize", "improve", "change how X works", "enhance", "update the…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before starting multi-step implementation work when no ordered task breakdown exists yet. Use when the requirement is confirmed and clear, and you need to answer "how do we build this and in what order" — producing an ordered task list with skill assignments and acceptance criteria. Stronger…

hellotern/Sextant

Skill Claude CodeCodex

Fallback for general coding work that does not match any specific sextant sub-skill. Use for lightweight tasks: config changes, style fixes, utility functions, one-off scripts, or tasks too small to warrant a dedicated workflow. All dedicated sub-skills take priority over this one — check these first: sextant:fix-bug…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before writing any design or code when the requirement is vague, ambiguous, or too broad. Use when the "what" is unclear — the requirement needs scoping, feasibility assessment, or decomposition before anyone touches code. Stronger signals: "unclear requirements", "break this down", "is this…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before evaluating, commenting on, or giving feedback on any code. Use when the primary request is to assess existing code — quality, correctness, style, or readiness to merge. Stronger signals: "review", "PR", "pull request", "code review", "check this code", "is this correct", "review this…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before approving or merging any code that touches auth, input handling, permissions, or external data. Use when the review focus is specifically on security vulnerabilities, attack surface, or compliance — not general code quality. Stronger signals: "security review", "check for…

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before creating a PR, bumping a version, or declaring work ready to merge. Use when the implementation is done and the goal is to get it across the finish line — PR creation, changelog, version bump, final pre-merge checks. Stronger signals: "ship this", "create a PR", "write changelog", "bump…

hellotern/Sextant

Skill Claude CodeCodex

Internal reference always included by sextant sub-skills. Not intended for direct invocation. Provides enhanced tool-call guidance for all sextant workflows: context, impact, query, trace, diffreview, and rename MCP tools. Apply its guidance only when GitNexus MCP tools are actually callable in the environment.

hellotern/Sextant

Skill Claude CodeCodex

You MUST use this skill before writing any test cases or adding test coverage. Use when the goal is to verify code behavior through tests — new tests, missing coverage, or a reproduction test after a bug fix. Stronger signals: "write tests", "add tests", "unit test", "integration test", "test coverage", "TDD", "test…