Skip to content

feat(skills): add migrating-private-integration skill#43

Open
TheRealAgentK wants to merge 1 commit into
masterfrom
feat/42/migrating-private-integration-skill
Open

feat(skills): add migrating-private-integration skill#43
TheRealAgentK wants to merge 1 commit into
masterfrom
feat/42/migrating-private-integration-skill

Conversation

@TheRealAgentK
Copy link
Copy Markdown
Collaborator

Closes #42

Summary

Adds a new skill skills/migrating-private-integration/SKILL.md that documents the end-to-end process for moving an integration from the private Autohive-AI/integrations repo to the public Autohive-AI/autohive-integrations repo.

Why

Triggered by the Gmail migration. The process needs to be repeatable, auditable, and consistently safe — particularly the security/safety/secrets review that gates whether anything can be published at all. We can't rely on every engineer remembering to do every check; the skill captures the checklist.

What's covered

The skill is structured as seven steps + reference material:

  1. Security / safety / secrets review — mandatory, with concrete grep recipes for hardcoded secrets, internal hostnames/employees, trade secrets, .env files, GitHub secret scanner usage, and binary/EXIF checks.
  2. Identify and drop legacy artefacts — vendored SDK copies, manual argparse --token harnesses, build caches, internal-only docs.
  3. Copy and adapt files — minimal file set, README rewrite to public-repo style, repo-level README updates on both sides.
  4. Local validationvalidate_integration.py, check_code.py, pytest, with auto-fix commands.
  5. Coordinate three PRs — branch naming, Conventional Commit titles, required PR-body content, merge order.
  6. Ask in the AH engineering Slack channel — explicitly required, with a sample message and a "wait for an explicit thumbs-up" rule.
  7. Post-merge cleanup — verify READMEs, follow-up issues for other repos that reference the old path.

Plus a "Common Failures and Fixes" table and a link to the Gmail migration as a worked example.

Companion PRs

Documents the process for moving an integration from the private
`Autohive-AI/integrations` repo to the public
`Autohive-AI/autohive-integrations` repo.

Triggered by the Gmail migration. Captures the full workflow:
  * Mandatory security/safety/secrets review (with grep recipes)
  * Identifying and dropping legacy artefacts (vendored SDK,
    manual harness, build caches)
  * Adapting structure to public repo conventions (empty
    __init__.py, public-style README, repo-level README updates)
  * Local validation via the tooling repo
  * Coordinating three PRs across public, private, and SDK repos
  * Required ask in the AH engineering Slack channel for a second
    pair of eyes before merging

References the Gmail migration as a worked example.

Closes #42
@github-actions
Copy link
Copy Markdown

Coverage — 4e8bf2b (feat(skills): add migrating-private-integration skill) by @TheRealAgentK

Total coverage: 100%

File Stmts Miss Cover Missing
src/autohive_integrations_sdk/__init__.py 2 0 100%
src/autohive_integrations_sdk/integration.py 358 0 100%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(skills): add migrating-private-integration skill

1 participant