Audit Value Delivery compliance after PR push
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Run after PR push to verify Value Delivery rules were followed during the session.
Collect data from the current session:
| Data Point | Source |
|---|---|
| Commit count | git rev-list origin/develop..HEAD --count |
| Files changed | git diff origin/develop --name-only | wc -l |
| Lines of code | git diff origin/develop --stat | tail -1 |
| console.log presence | Grep in changed files |
| Metric | Current | Threshold | Status |
|---|---|---|---|
| Lines of Code | [N] | 300 | OK/CROSSED ([X]x) |
| Files Changed | [N] | 10 | OK/CROSSED ([X]x) |
| Commits | [N] | 5 | OK/CROSSED ([X]x) |
| console.log | [N] | 0 | OK/CROSSED |
Verdict: [PASSED / TRIGGER_PR - Should have pushed earlier PRs]
| Requirement | Expected | Actual | Status |
|---|---|---|---|
| Session Headers/Footers | Every response | [Count] | Done/Missing |
| pr-review skill format | Full report | [Format] | Done/Partial/Missing |
| qa-commit skill format | Full criteria table | [Format] | Done/Partial/Missing |
| pr-threshold checks | After each commit | [Count] | Done/Partial/Missing |
| Risk Assessment | Calculate score | [Done/Not] | Done/Missing |
| Storybook stories | For new components | [Count] | Done/Missing |
| Design system check | Before new patterns | [Done/Not] | Done/Partial/Missing |
| Satisfies field in commits | Every commit | [Count] | Done/Missing |
| Typecheck/Lint | Before commits | [Done/Not] | Done/Missing |
## Value Delivery Compliance Audit
### PR Threshold Check
| Metric | Current | Threshold | Status |
|--------|---------|-----------|--------|
| Lines of Code | [N] | 300 | [status] |
| Files Changed | [N] | 10 | [status] |
| Commits | [N] | 5 | [status] |
| console.log | [N] | 0 | [status] |
**Verdict:** [PASSED / TRIGGER_PR]
### Gaps Identified
| Requirement | Expected | Actual | Status |
|-------------|----------|--------|--------|
| [requirement] | [expected] | [actual] | [status] |
...
### Recommendations
[List any improvements for next session]
If using Notion sync, add compliance report to Session Journal entry.
The audit should produce a table matching the format shown in the user's compliance screenshot, with clear CROSSED indicators for threshold violations and status icons for gap analysis.
This skill is invoked by:
push-pr.mdc - After PR is created (Phase 4)Invoked automatically after PR push, or manually with "use compliance-audit skill".
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.
The English summary is being prepared. Showing the original description.
Iterate until success or limit, composing existing skills with Jidoka integration
The English summary is being prepared. Showing the original description.
Build a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.
The English summary is being prepared. Showing the original description.
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
The English summary is being prepared. Showing the original description.
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.
The English summary is being prepared. Showing the original description.
Review code changes against hard rules and conventions
The English summary is being prepared. Showing the original description.