docs(project-management): confirm repo ownership explicitly, don't infer from namespace - #2510
Open
wesleymatosdev wants to merge 2 commits into
Open
Conversation
…fer from namespace A repo under a familiar org/user namespace can still belong to someone else - the captain can be a user or contributor without owning it. Getting this wrong misleads every later delivery-mode and PR-content decision for that project.
There was a problem hiding this comment.
Pull request overview
Captain, this PR updates the project-management skill documentation to explicitly require confirming repository ownership (instead of inferring it from a familiar namespace/description), to avoid downstream mistakes when recording a project and deciding delivery/PR behavior later.
Changes:
- Add a new instruction in “Add or clone an existing project” to confirm true repo ownership explicitly (don’t infer from org/user namespace or repo description).
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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
The project-management skill's "Add or clone an existing project" section didn't say to confirm actual repo ownership before recording it — a repo under a familiar org/user namespace can still belong to someone else, since a user can be a contributor without owning the repo.
Adds one line: confirm ownership explicitly rather than inferring it from a matching namespace or repo description, since getting this wrong misleads later delivery-mode and PR-content decisions for that project.
Testing
Docs-only change, no code affected.