Back to list
rjmurillo

session

by rjmurillo

Multi-agent system for software development

5🍴 0📅 Jan 24, 2026

SKILL.md


Session Skills

Skills for session management and protocol compliance.

Triggers

PhraseAction
"Check if I can skip QA"Run Test-InvestigationEligibility.ps1
"Am I eligible for investigation-only?"Verify staged files against ADR-034 allowlist
"Verify investigation session eligibility"Check QA skip eligibility before commit
"Can I use SKIPPED: investigation-only?"Validate investigation-only exemption
"Test eligibility for QA skip"Execute eligibility check script

Process

Phase 1: Eligibility Check

StepActionToolOutput
1.1Stage files for commitgit addFiles added to staging area
1.2Run eligibility checkTest-InvestigationEligibility.ps1JSON with Eligible, StagedFiles, Violations
1.3Verify Eligible=trueParse JSON outputBoolean result

Phase 2: Commit Decision

StepActionConditionNext Step
2.1Proceed with investigation-only skipEligible=true, Violations=[]Use "SKIPPED: investigation-only"
2.2Address violations or invoke qa agentEligible=falseFix violations or start new session

Quick Reference

SkillPurposeWhen to Use
Test-InvestigationEligibilityCheck if staged files qualify for investigation-only QA skipBefore committing with SKIPPED: investigation-only

Test Investigation Eligibility

Check if staged files qualify for investigation-only QA skip per ADR-034.

Trigger Phrases

  • "Check if I can skip QA"
  • "Am I eligible for investigation-only?"
  • "Verify investigation session eligibility"
  • "Can I use SKIPPED: investigation-only?"

Usage

pwsh .claude/skills/session/scripts/Test-InvestigationEligibility.ps1

Output

Returns JSON with:

FieldTypeDescription
Eligiblebooleantrue if all staged files are in allowlist
StagedFilesarrayAll staged file paths
ViolationsarrayFiles not in allowlist (empty if eligible)
AllowedPathsarrayReference list of allowed path prefixes
ErrorstringPresent only on git errors

Exit Codes

CodeMeaning
0Success (eligibility result in JSON output)

Note: The script always exits 0. Check the Eligible field in the JSON output to determine eligibility. The Error field is present when git commands fail.

Error Handling

ScenarioBehaviorOutput
Not in git repositoryReturns JSON with Eligible: falseError field explains the issue
Git command failsReturns JSON with Eligible: falseError field explains the issue
Empty staged filesReturns JSON with Eligible: trueStagedFiles is empty array
Mixed allowed/disallowed filesReturns JSON with Eligible: falseViolations lists disallowed files

Example Outputs

Eligible (investigation-only files):

{
  "Eligible": true,
  "StagedFiles": [".agents/sessions/2025-01-01-session-01.md"],
  "Violations": [],
  "AllowedPaths": [
    ".agents/sessions/",
    ".agents/analysis/",
    ".agents/retrospective/",
    ".serena/memories/",
    ".agents/security/"
  ]
}

Not eligible (contains code files):

{
  "Eligible": false,
  "StagedFiles": [
    ".agents/sessions/2025-01-01-session-01.md",
    "scripts/MyScript.ps1"
  ],
  "Violations": ["scripts/MyScript.ps1"],
  "AllowedPaths": [
    ".agents/sessions/",
    ".agents/analysis/",
    ".agents/retrospective/",
    ".serena/memories/",
    ".agents/security/"
  ]
}

Git error:

{
  "Eligible": false,
  "StagedFiles": [],
  "Violations": [],
  "AllowedPaths": [
    ".agents/sessions/",
    ".agents/analysis/",
    ".agents/retrospective/",
    ".serena/memories/",
    ".agents/security/"
  ],
  "Error": "Not in a git repository or git command failed"
}

Agent Workflow Integration

SESSION-PROTOCOL.md Relationship

This skill implements the verification step for Phase 2.5: QA Validation of the Session End Protocol:

SESSION-PROTOCOL.md (Phase 2.5: QA Validation)
                │
                ├── Feature implementation → MUST invoke qa agent
                │
                └── Investigation session → MAY skip QA
                        │
                        └── Test-InvestigationEligibility.ps1
                                │
                                ├── Eligible: true → Use "SKIPPED: investigation-only"
                                │
                                └── Eligible: false → MUST invoke qa agent

Workflow: Before Committing Investigation Work

1. Stage your files
   │
   └── git add .agents/sessions/... .serena/memories/...

2. Run eligibility check
   │
   └── pwsh .claude/skills/session/scripts/Test-InvestigationEligibility.ps1

3. Check output
   │
   ├── Eligible: true
   │   └── Safe to commit with "SKIPPED: investigation-only"
   │
   └── Eligible: false
       │
       ├── Check Violations array
       │   └── Either: Remove violating files from staging
       │   └── Or: Start new session for implementation work
       │
       └── Invoke qa agent for the implementation work

Integration with Session End Checklist

Use this skill to validate the QA skip condition:

### Session End (COMPLETE ALL before closing)

| Req | Step | Status | Evidence |
|-----|------|--------|----------|
| MUST | Route to qa agent (feature implementation) | [x] | `SKIPPED: investigation-only` - Verified via Test-InvestigationEligibility.ps1 |

Allowed Paths (Investigation Allowlist)

These paths qualify for investigation-only QA exemption:

PathPurpose
.agents/sessions/Session logs documenting work
.agents/analysis/Investigation outputs and findings
.agents/retrospective/Learnings and retrospective documents
.serena/memories/Cross-session context storage
.agents/security/Security assessments and reviews

Important: This allowlist is defined by ADR-034 (Investigation Session QA Exemption). The patterns in Test-InvestigationEligibility.ps1 are validated by Pester tests to ensure they match the ADR specification.


Anti-Patterns

AvoidWhyInstead
Skipping eligibility checkMay commit ineligible files with investigation-only skipAlways run the skill before using the skip
Ignoring violationsQA exemption won't be validAddress violations or invoke qa agent
Using for code changesInvestigation-only is for analysis, not implementationStart a new session for code work
Hardcoding path checksPatterns may drift from ADR-034 specificationUse this skill which implements the ADR patterns

Verification Checklist

After using this skill:

  • Skill output shows Eligible: true
  • No Violations in output
  • No Error field in output
  • Session log evidence updated with skill output

ReferenceDescription
ADR-034Investigation Session QA Exemption architecture decision
SESSION-PROTOCOL.mdSession start/end requirements (Phase 2.5)
Issue #662Create QA skip eligibility check skill
Validate-SessionJson.ps1Validates session JSON format (separate from eligibility)
Test-InvestigationEligibility.Tests.ps1Pester tests ensuring pattern consistency

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

0/5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon