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 logic". Use sextant:add-feature instead when the thing being built does not yet exist. Use sextant:fix-bug instead when the existing behavior is broken and needs to be restored.
EnglishYou 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 feasible", "help me design", "what do we need to build", vague one-sentence feature requests, open-ended asks like "build me X". Skip this skill and go directly to sextant:add-feature only when the requirement is already concrete, scoped, and unambiguous.
EnglishInternal 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.
English
AGENT SKILLS ATLASIncludes Modify Feature, Refine Requirements, and Tool Gitnexus.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Modify Feature
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 logic". Use sextant:add-feature instead when the thing being built does not yet exist. Use sextant:fix-bug instead when the existing behavior is broken and needs to be restored.
Refine Requirements
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 feasible", "help me design", "what do we need to build", vague one-sentence feature requests, open-ended asks like "build me X". Skip this skill and go directly to sextant:add-feature only when the requirement is already concrete, scoped, and unambiguous.
Tool Gitnexus
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.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Modify Feature skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.