post-change-pipeline
Skill2 starsChanged 46 days agoApache-2.0View on GitHub
Mandatory impact analysis before any commit to the Agentica repository — identifies which files changed, what downstream updates that requires (site rebuild, ADR, CSS token regeneration), presents the impact as a report, and waits for explicit human approval before executing anything. Use before every commit, however small.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-component-metadataSkill
- ai-ds-composerSkill
- codebase-indexSkill
- documentSkill
- post-change-pipelineSkill
- quality-gateSkill
- ux-pattern-reviewSkill
- ai-component-metadataSkill
- ai-ds-composerSkill
- codebase-indexSkill
- documentSkill
- quality-gateSkill
- ux-pattern-reviewSkill
- design-system-builderSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Run git diff --name-only and git diff --cached --name-only to identify modified files.
- Distinctive: line 77
Create the approved ADRs
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: post-change-pipeline
Mandatory pipeline before any commit — analyzes the impact of changes and submits a report for human approval. Type: skill Logical path: .claude/skills/post-change-pipeline/SKILL.md Read before: AGENTS.md, governance/rules/git-workflow.md, governance/rules/tokens-system.md Relations: site/build.js, tokens/, decisions/, decisions/ADR-069-migration-suivi-projet-github-projects.md
Trigger
This pipeline runs mandatorily after every modification and before every commit. It cannot be skipped, even for a minor change.
Step 1 — Impact analysis (automatic)
Run git diff --name-only and git diff --cached --name-only to identify modified files.
Apply the impact matrix:
| Modified files | Updates to evaluate |
tokens/primitives.json | Site rebuild, log, ADR if new token or palette |
tokens/semantic.json | Site rebuild, log, generated tokens.css |
tokens/component.json | Site rebuild, log, Principal Designer approval required |
site/build.js | Site rebuild only |
site/dist/ | Log only (dist is an output) |
guidelines/ or components/ | Site rebuild, log |
decisions/ADR-*.md | Site rebuild (ADR page), log |
governance/rules/ or .claude/skills/ | Log |
AGENTS.md, DESIGN.md, README.md | Log |
Tracking for this work (status, domain) lives in GitHub Projects (ADR-069) — not in a file in the repo, so there is nothing to propose on the log side for this reason.
Step 2 — Impact report (present to the human)
Present a structured report before any commit:
## Change impact — approval required
### Modified files
- [list of files from git diff]
### Proposed updates
- [ ] Site rebuild (`node site/build.js`) — [reason]
- [ ] ADR-XXX to create — [proposed title] — if architectural decision
- [ ] CSS tokens to regenerate — if tokens modified
- [ ] Other: [description]
### Points of attention
- [Any component token modification → approval reminder]
- [Any new token → suggest an ADR]Do not commit before an explicit response from the human.
Step 3 — Execution (only after approval)
Execute only the approved tasks, in this order:
- Regenerate CSS tokens if
tokens/was modified - Rebuild the site if approved (
node site/build.js) - Create the approved ADRs
- Stage and commit all files in a single coherent commit
Escalation rules
- Modification of
tokens/component.json→ explicitly mention that Principal Designer approval is required - New primitive or semantic token → propose an ADR
- Removal of a token → block and request a full impact audit
Anti-patterns
❌ Committing without presenting the impact report
❌ Rebuilding the site without it being approved
❌ Updating the log after the commit rather than before
❌ Proposing all updates even when not relevant (use the matrix)
❌ Waiting for the human to ask for the log — always propose itDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

