Skip to content

docs(verify): harden verify secret handling #377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
codeaholicguy wants to merge 1 commit into from
Closed

docs(verify): harden verify secret handling #377

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions skills/verify/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ Prove it works before saying it works.
- Do not claim completion without fresh terminal evidence from this session.
- Forbidden words in completion claims: "should", "probably", "seems to", "likely", "I believe", "I think it works". These signal unverified assertions.
- Cached, remembered, or previous-session output is not evidence. Run it again.
- Never print, log, store, or relay secrets. Before citing command output, redact values that look like tokens, API keys, passwords, or credentials; cite the exit code and summarized key output rather than raw dumps.

## Gate Function

Expand All @@ -21,7 +22,7 @@ Every completion claim must pass all 5 steps in order:
2. **Run** — Execute the full command now. No partial runs, no skipping.
3. **Read** — Read complete output. Check exit code. Count pass/fail.
4. **Confirm** — Does the output prove the exact claim?
5. **Report** — State the result, cite command, exit code, and key output.
5. **Report**: State the result, cite command, exit code, and key output with secrets redacted.

If any step fails, stop. Fix the issue and restart from step 1.

Expand Down Expand Up @@ -64,7 +65,7 @@ If step 4 passes, the test is wrong. Rewrite it.

## Memory Integration

After a failed verification, store the failure pattern: `npx ai-devkit@latest memory store --title "<failure pattern>" --content "<what failed and how to avoid>" --tags "verify,failure-pattern"`
After a failed verification, store the failure pattern (redact any secrets from the content first): `npx ai-devkit@latest memory store --title "<failure pattern>" --content "<what failed and how to avoid>" --tags "verify,failure-pattern"`

## Task Tracing

Expand Down
Loading