This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git
The following commit(s) were added to refs/heads/main by this push:
new cf910bc docs(contributing): document skillOverrides for local
development (#101)
cf910bc is described below
commit cf910bcd339553db4ce8f377b8bb08f551d3eab8
Author: Yeonguk Choo <[email protected]>
AuthorDate: Sun May 10 20:11:33 2026 +0900
docs(contributing): document skillOverrides for local development (#101)
---
CONTRIBUTING.md | 43 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 80ed2ba..f5e2c9a 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,6 +6,7 @@
- [Project structure](#project-structure)
- [Directory tree](#directory-tree)
- [Getting set up](#getting-set-up)
+ - [Lightening the agent context](#lightening-the-agent-context)
- [Making changes](#making-changes)
- [Running the dev loop](#running-the-dev-loop)
- [Opening a pull request](#opening-a-pull-request)
@@ -184,6 +185,48 @@ Read
[`.claude/skills/setup-steward/adopt.md`](.claude/skills/setup-steward/adop
configuration tutorial, including the placeholder convention and how
the skills consume both layers.
+### Lightening the agent context
+
+Most skills in this repository are runtime workflows for adopters
+(security triage, PR management, CVE allocation). They have no use
+while you are *editing the framework itself*, but they still load
+into the agent's context window and crowd out the files you actually
+need to read.
+
+Opt out per skill by adding a `.claude/settings.local.json` to your
+clone (gitignored) and listing the skills you want disabled:
+
+```json
+{
+ "$schema": "https://json.schemastore.org/claude-code-settings.json";,
+ "skillOverrides": {
+ "pr-management-code-review": "off",
+ "pr-management-mentor": "off",
+ "pr-management-stats": "off",
+ "pr-management-triage": "off",
+ "security-cve-allocate": "off",
+ "security-issue-deduplicate": "off",
+ "security-issue-fix": "off",
+ "security-issue-import": "off",
+ "security-issue-import-from-md": "off",
+ "security-issue-import-from-pr": "off",
+ "security-issue-invalidate": "off",
+ "security-issue-sync": "off",
+ "setup-isolated-setup-install": "off",
+ "setup-isolated-setup-update": "off",
+ "setup-isolated-setup-verify": "off",
+ "setup-override-upstream": "off",
+ "setup-shared-config-sync": "off",
+ "setup-steward": "off",
+ "write-skill": "on"
+ }
+}
+```
+
+The file is per-clone and per-user; nothing from it gets committed.
+Flip a skill back to `"on"` (or remove the entry) when you start
+working on that area.
+
## Making changes
Think about **which layer the change belongs in** before you start
