Skip to content

chore(skills): add verify skill - #367

Open
labgadget015-dotcom wants to merge 1 commit into
mainfrom
chore/verify-skill
Open

labgadget015-dotcom wants to merge 1 commit into
mainfrom
chore/verify-skill

Conversation

@labgadget015-dotcom

Copy link
Copy Markdown
Owner

Summary

Follow-up to #366 (squash-merged before this commit was pushed). Adds .claude/skills/verify/SKILL.md — how to verify changes in this repo at their real surface:

  • Read Actions logs via the jobs/check-runs API (gh run view --log often returns empty).
  • Which workflows are safe to dispatch (Intake Canary) vs paid/side-effecting (drc-e2e-canary.yml — do not dispatch without asking).
  • Replaying the Neon canary SQL locally, read-only, without printing the DSN.

Docs only — no runtime code, workflows, config/ or core/.

🤖 Generated with Claude Code

…rface

Covers reading Actions runs/logs via the API (gh run view --log is often
empty), which workflows are safe to dispatch vs paid (drc-e2e-canary), and
replaying the Neon canary SQL read-only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 22, 2026 06:45
@github-actions

Copy link
Copy Markdown
Contributor

🟢 Risk Assessment: LOW (0.0/10)

Analysed 1 files, 25+ / 0− lines. Test coverage unchanged or improved.

Scoring breakdown

Factor Score

✅ Eligible for auto-merge (subject to CI passing).

@github-actions

Copy link
Copy Markdown
Contributor

🤖 Elite AI Copilot Analysis

Elite AI Copilot Analysis Report

Generated: 2026-10-22 06:46:13
Session ID: copilot_1792651573
Repository: .

🎯 Health Score: 100.0/100

🚀 Top Recommendations

  1. ✅ Repository is in excellent shape - continue current practices

📊 Detailed Insights

Code Quality Baseline Established

  • Category: code_quality
  • Severity: info
  • Description: Repository code quality metrics captured
  • Suggested Action: Continue monitoring for regressions
  • Confidence: 90%

Security Scan Initiated

  • Category: security
  • Severity: info
  • Description: No critical vulnerabilities detected in initial scan
  • Suggested Action: Enable continuous security monitoring
  • Confidence: 85%

Repository Structure Analyzed

  • Category: architecture
  • Severity: info
  • Description: Well-organized modular structure detected
  • Suggested Action: Maintain separation of concerns
  • Confidence: 80%

Performance Baseline Captured

  • Category: performance
  • Severity: info
  • Description: Repository performance metrics recorded
  • Suggested Action: Monitor for performance regressions
  • Confidence: 75%

Documentation Structure Good

  • Category: documentation
  • Severity: info
  • Description: Comprehensive documentation files present
  • Suggested Action: Keep documentation in sync with code changes
  • Confidence: 90%

Powered by Elite AI Copilot v1.0

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Pre-commit Checks

✅ All pre-commit checks passed!

Your code follows the project style guidelines.


Pre-commit hooks help maintain code quality and consistency.

@github-actions

Copy link
Copy Markdown
Contributor

🔒 Security Scan Results

🛡️ Bandit Security Scan

  • 🔴 HIGH: 0
  • 🟡 MEDIUM: 5
  • 🟢 LOW: 107

📦 Dependency Vulnerabilities

  • Total vulnerable dependencies: 62

Vulnerable Dependencies:

  • pygithub 2.10.0
  • aiohttp 3.14.5
  • multidict 7.1.0
  • yarl 1.25.1
  • pyyaml 6.0.3
  • ... and 57 more

Security scans run automatically on every PR. View detailed reports in the Actions tab.

@labgadget015-dotcom

Copy link
Copy Markdown
Owner Author

🤖 DRC Agent Analysis

Recommendation: 🟠 P1 IMPORTANT

Summary: Structured Skill + Verification Runbook (Dreamer ID 2, Realist Recommended)

Next steps:

  1. Step 1: Create .claude/skills/verify/ directory and author SKILL.md with YAML frontmatter (id: verify, version: 1.0.0, last-updated, triggers, cost_risk) — dispatch table must use explicit BLOCKED/SAFE/PAID labels, not prose
  2. Step 2: Create .claude/skills/verify/runbook.md with labeled copy-paste blocks for gh api check-runs call, safe intake-canary dispatch, and psql read-only replay with DSN_ENV_VAR pattern and inline NEVER ECHO comment
  3. Step 3: Create .claude/skills/skills_index.yaml listing the verify skill with path, version, and one-line description
  4. Step 4: Add CI validation using python3 -c yaml.safe_load() on all .claude/skills/**/*.yaml and SKILL.md frontmatter — no new dependencies
  5. Step 5: Add CI check verifying every .claude/skills/ subdirectory has a corresponding skills_index.yaml entry

Strategic fit: Consulting: high · Product: medium · Tech debt: reduces


Analysed by GadgetLab DRC Agent (Dreamer → Realist → Critic) · Run run_1792651537020

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The verification instructions can cause unexpected live notifications and false local canary failures.

2 open issues
What changed in this PR

Adds a verification skill that complements #366’s local agent tooling with guidance for checking GitHub Actions and replaying canary checks. This is documentation-only; runtime behavior is unchanged.

Changes:

  • Documents API-based access to Actions logs and annotations.
  • Describes workflow dispatch precautions.
  • Outlines read-only local canary SQL replay without exposing credentials.
File Description
.claude/​skills/​verify/​SKILL.md Adds repository-specific verification guidance for Actions and canary checks.

Review effort: Balanced

- `gh run view --log` often returns EMPTY. Use the API instead:
`gh api repos/labgadget015-dotcom/autonomous-github-agent/actions/jobs/<job_id>/logs`
and `.../check-runs/<job_id>/annotations` (canary verdicts are `::notice::`/`::error::`).
- Read-only workflows (Intake Canary) are safe to `gh workflow run <file> --ref main`.
Comment on lines +24 to +25
- Replay the workflow's exact SQL: awk the `<<'SQL'` heredoc out of the yml, pipe psql output
into `python3 .github/scripts/intake_canary_neon.py` with `GITHUB_OUTPUT=$(mktemp)`.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants