What inline learns
Skills
A skill is a document of review expertise that inline loads when the code it covers comes up. Write your compliance checks, your domain rules or your architecture guidance once, and attach that skill wherever it applies.
Writing and attaching skills is an admin task. Everyone else sees the result in reviews of the repositories a skill covers.
#What a skill is for
Reach for a skill when what you want to give inline runs to paragraphs: how your team handles patient data, what your payments code must never do, the reasoning behind an architecture.
Where the thing you want to say fits in one sentence, Learnings is the quicker home for it, and you can teach one from a pull request without opening the portal.
#Writing one
Skills
Reusable review expertise — compliance checks, domain rules, architecture guidance. Attach a skill to every repo or to specific ones; the reviewer loads it when the code matches.
Edit skill
Description
What this skill checks AND when to use it — the reviewer decides from this sentence whether to load the skill, so be specific about the code it applies to.Apply to all repositories
Skill body (markdown)
Check every handler that touches PHI for an audit log entry.Choose Create skill and name it.
Names read like identifiers: hipaa-phi-handling, billing-money-rules.Write the Description, and take care over it.
This is the sentence inline reads to decide whether a change needs this skill, so say what the skill checks and which code it applies to.Write the Skill body (markdown).
The expertise itself, as long as it needs to be. Headings, lists and examples all work.Decide where it applies.
Apply to all repositories attaches it everywhere. Leaving it off means you attach the skill per repository instead.
#When inline uses one
During a review, inline reads the descriptions of the skills attached to that repository and loads the ones whose code the change touches. A skill about payments stays unread on a documentation change.
That is why a workspace can carry many skills without every review reading all of them.
#Attaching a skill to a repository
A skill marked Apply to all repositories is attached everywhere already. For the rest, open the repository and use the Skills card in Repository settings, or set the workspace-wide list under Workspace skills in Review config.
The Enabled switch on a skill turns it off across the whole workspace at once, which is the quicker move when you want to stop using one everywhere.
Skills are included with Pro. See Plans and billing.