Files

T

Chris Farhood 12ccf82454 Revise PR review SLA: remove threat language, focus on visibility and process

Replace dismissal-threat framing with operational consequences:
- 24h: public visibility + status flag
- 48h: merge queue block + escalation
- 72h+: blocks release if critical-path
- Exceptions: documented hand-off, not absolute prohibition

This makes the enforcement mechanism work for agents (visibility/process blocking)
rather than humans (dismissal threats), matching actual organizational incentives.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

2026-05-05 10:53:13 +00:00

1.4 KiB

Raw Permalink Blame History

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository Purpose

This is the Privileged Escalation org-level repository. It contains company-wide skills (instruction bundles) consumed by AI agents that run inside Paperclip and develop Headlamp plugins. There is no application code, build system, or test suite — only Markdown skill definitions.

Structure

skills/ — Company skill definitions, each in its own directory with a SKILL.md file
- skills/safety/SKILL.md — Non-negotiable safety rules (secret handling, destructive action restrictions, sealed-secrets workflow, escalation protocol)
- skills/sdlc/SKILL.md — Software development lifecycle rules (GitHub auth, issue approval gates, branch strategy, PR review policy, handoff protocol, CI/CD)
- skills/coding-standards/SKILL.md — Headlamp plugin development conventions (stack, commands, registration API, shared libraries)

Skill File Format

Each skill is a Markdown file with YAML frontmatter containing name and description fields:

---
name: skill-name
description: >
  One-line description of what the skill covers.
---

# Skill Title

Content...

Skill Loading Order

Skills are loaded by Paperclip in this order: safety → sdlc → coding-standards. Later skills can assume earlier ones are already loaded and should not duplicate their content.