diff --git a/.agents/skills/identify-gaps/SKILL.md b/.agents/skills/identify-gaps/SKILL.md index e5e956e54d4..6d82fb8f415 100644 --- a/.agents/skills/identify-gaps/SKILL.md +++ b/.agents/skills/identify-gaps/SKILL.md @@ -33,7 +33,10 @@ with the last one. Pick out the things a reader would act on: code samples, function names, flags, button labels, defaults, versions, limits. Check each against the code: `OpenFn/lightning` for the web app, `OpenFn/kit` for the CLI, `OpenFn/adaptors` -for adaptor functions. Note the file and line. Anything you cannot check from +for adaptor functions. Check the latest `main`, not a local checkout, which may +be on another branch: `git clone --depth 1 https://github.com/OpenFn/.git +/tmp/`, or `git pull` it if it is already there. Note the file and line, +and the commit you checked. Anything you cannot check from code, such as pricing, policy, or per-deployment settings, is a question for the product team. Try each external link twice: a 404 or 410 means it is dead, but a 403 or 429 does not. diff --git a/.agents/skills/translate/SKILL.md b/.agents/skills/translate/SKILL.md index b2d37caf3dc..888028d10e2 100644 --- a/.agents/skills/translate/SKILL.md +++ b/.agents/skills/translate/SKILL.md @@ -80,9 +80,12 @@ Build the whole site, not just your locale. `yarn build --locale ` builds the locale at the site root, so every correct `/es/...` link shows up as broken. -Open one PR per locale, separate from the English PR. Translated files do not -count toward the 20-file limit, because a locale's translations are reviewed as -a set. In the PR description, say which tool and model translated the text. If +Open one PR per locale, separate from the English PR. Commit each locale on its +own branch, created from the current one and named after it plus the locale, +such as `fix-alerts-es`. If the English is not on `main` yet, open the PR +against the English branch and say so in the description. Translated files do +not count toward the 20-file limit, because a locale's translations are reviewed +as a set. In the PR description, say which tool and model translated the text. If you spot a problem in the English while translating, list it in the PR description under "Problems in the English", with the file and line. Do not fix it in this PR.