You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f3fcc75
Browse filesBrowse the repository at this point in the historyBrowse files
8. Call out risks, unknowns, and decisions that need stakeholder input.
151
+
9. Assess **LSM compatibility** — if the change touches process identity, `/proc` filesystem access, binary execution, or inter-process visibility, flag whether it will behave differently on hosts running SELinux (enforcing) or AppArmor. In particular, tests that fork+exec into system binaries will fail on SELinux-enforcing hosts due to cross-label `/proc/<pid>/exe` access restrictions.
Copy file name to clipboardExpand all lines: .agents/skills/create-spike/SKILL.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,9 @@ The prompt to the reviewer **must** instruct it to:
91
91
92
92
9.**Check architecture docs** in the `architecture/` directory for relevant documentation about the affected subsystems.
93
93
94
-
10.**Determine the issue type:**`feat`, `fix`, `refactor`, `chore`, `perf`, or `docs`.
94
+
10.**Assess Linux Security Module (LSM) impact.** If the change involves process identity, `/proc` filesystem access, file labeling, binary execution, or inter-process visibility, call out whether it will behave differently on hosts running SELinux (enforcing) or AppArmor. For example: reading `/proc/<pid>/exe` across an SELinux domain boundary returns ENOENT, not EACCES. Tests that fork+exec into system binaries (different SELinux label) will fail on enforcing hosts. Flag any LSM-sensitive code paths and recommend mitigations.
95
+
96
+
11.**Determine the issue type:**`feat`, `fix`, `refactor`, `chore`, `perf`, or `docs`.
0 commit comments