Add repo-orient skill for codebase orientation before edits#1663
Open
Gowtham-Pentela wants to merge 1 commit into
Open
Add repo-orient skill for codebase orientation before edits#1663Gowtham-Pentela wants to merge 1 commit into
Gowtham-Pentela wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
repo-orientskill for understanding unfamiliar repositories before planning, reviewing, debugging, or editing code.The skill checks for existing repo-map artifacts such as:
docs/ARCHITECTURE_REPORT.mddocs/PROJECT_MAP.mddocs/project_map.jsongraphify-out/GRAPH_REPORT.mdgraphify-out/graph.jsonAGENTS.mdCLAUDE.mdThen it produces a grounded orientation report covering architecture, entry points, dependency hubs, feature ownership, risk areas, files to inspect, and recommended next action.
Why
AI coding agents often make poor edits when they start implementation before understanding project structure. This skill creates a consistent pre-edit orientation step that can be used before
investigate,review,qa, orship.Notes
This is a workflow-only skill. It introduces no runtime dependencies and no external API calls.