Keep repository contribution guidance consistent after workflow changes. Compare agent skills, coding guidance, contributor documentation, and issue and pull request templates, then fix contradictory instructions, outdated references, and mismatched inventories.
Reconcile contributor skills, AGENTS.md, CONTRIBUTING.md, issue and PR templates, and workflow references after repository workflow changes.
Review the instructions the agent will receive before you install.
Keep contributor guidance consistent without copying procedural workflows into AGENTS.md. That file holds repository coding conventions and pointers; the relevant skills hold issue, PR, and maintenance procedures. CONTRIBUTING.md explains the human workflow.
Run after adding, removing, or renaming a skill or crate; changing issue or PR conventions; changing development workflows; or modifying templates or agent cross references. Run before opening a PR that touches these areas.
| Change | Skills to inspect |
|---|---|
| Issues, triage, labels, or feature proposals | create-github-issue, triage-issue, review-triage-queue, apply-triage-action, create-spike, build-from-issue |
| PR template, vouch behavior, or review conventions | create-github-pr, review-github-pr, build-from-issue |
| Security assessment or remediation | review-security-issue, fix-security-issue |
| Published docs workflow | update-docs-from-commits |
| CLI commands, flags, defaults, or workflows | openshell-cli |
| Sandbox policy schema or enforcement | generate-sandbox-policy, openshell-cli |
| Gateway deployment, Helm, drivers, or health checks | debug-openshell-cluster, helm-dev-environment |
| Inference providers or native model endpoints | debug-inference, openshell-cli |
| TUI behavior | tui-development |
| Release artifacts or smoke coverage | test-release-canary |
| CI diagnostics | watch-github-actions |
| Gator supervision | launch-openshell-gator |
| SBOM workflow | sbom |
| RFC workflow | create-rfc |
Search both skills/ and .agents/skills/ for affected commands, fields, and components; the map is a starting point.
skills/*/SKILL.md and .agents/skills/*/SKILL.md with the inventories in CONTRIBUTING.md. Public skills must work outside a checkout and use installed CLI help and published documentation. Contributor skills must set metadata.internal: true. Confirm names are unique and local links resolve.crates/ with the architecture table in AGENTS.md. Check the public and contributor skill rows.CONTRIBUTING.md to retrieve every page of current GitHub labels and resolve unclear descriptions, then check issue guidance for the general triage → validation → human acceptance process. Skills should mention the state:* namespace without enumerating exact labels, and should not depend on agent:* labels. A direct request authorizes only the requested phase; unattended work uses current state descriptions, maintainer assignments, and comments to establish the authorized phase.create-github-issue, create-spike, and triage-issue for the first-hand OpenShell User Story, OpenShell-only bug reproduction, notional UX examples, and consideration of applicable extension points.create-github-pr, build-from-issue, fix-security-issue, and CONTRIBUTING.md: every PR must close an existing issue covering its scope, except automated dependency updates as described in CONTRIBUTING.md. Multi-PR work needs an issue per PR; a separate issue may track the overall effort.CONTRIBUTING.md; AGENTS.md and skills should refer to that convention. Check README.md, .github/ISSUE_TEMPLATE/, .github/workflows/, .agents/agents/, and related skill cross references for stale workflow statements. Keep user-facing documentation changes minimal and avoid duplicated internal explanations.CONTRIBUTING.md; they must not require full Rust, SDK, or repository CI for changes that cannot affect those areas.npx -y skills add . --list from a disposable clean copy when skill discovery changes. It should expose public skills only; clean generated files afterward.Fix contradictions, then repeat the affected checks. Report files changed and any remaining drift. Do not treat an old document's label list as a source of truth over current GitHub metadata.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Process one recommendation selected by ID from a local issue or CI triage report. Apply, reject, or defer it, record the outcome, and obtain separate confirmation before each change made on GitHub.
Turn a GitHub issue into a scoped implementation plan and, when authorized, code changes, tests, documentation, and a pull request that closes it. Check existing ownership and feedback to keep work aligned with acceptance criteria.
Maintain and validate OpenShell builds for Windows on x64 and ARM64 using MSVC, Microsoft's C++ toolchain. Check compilation, build executables, run tests on native hosts, and report artifacts and unsupported driver behavior.
Create GitHub issues for OpenShell bugs, feature requests, and tasks using the gh command-line tool. Organize firsthand use cases, impact, and completion criteria into the project's templates, then return the created issue link.
Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.
Turn a design request into an OpenShell RFC, a proposal for review and discussion. The skill follows the project template, assigns an available number, and organizes motivation, alternatives, and open questions into a draft.