Agent skill
gh-verifying-context
Verifies the current GitHub authentication status and git remote to ensure the agent is operating in the correct account and repository. Use at the start of every session.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/gh-verifying-context
SKILL.md
Verifying GitHub Context
Purpose
This skill ensures that the agent is aware of its identity (GitHub user) and location (repository and organization) before performing any actions. This prevents accidental data leakage between personal and work accounts.
1. Safety & Verification
- Mandatory First Step: This skill MUST be executed at the beginning of every interaction involving GitHub.
- Human Confirmation: The agent MUST report the results (User, Organization, Repository) to the user and wait for explicit confirmation that the context is correct.
2. Common Workflows
Workflow: Check Authentication and Remote
Retrieves current login and remote URLs.
Command:
gh auth status && git remote -v
3. Output Handling
The agent should parse the output and present it clearly:
- Logged in as: [username]
- Active Repository: [owner/repo]
- Remotes: [origin URL]
If the user or repository does not match the expected context for the task (e.g., work-related task in a personal repo), the agent MUST STOP and alert the user.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?