Skip to content

docs(skills): make destructive-test invocation safer by default#41

Open
TheRealAgentK wants to merge 1 commit into
masterfrom
docs/skill-destructive-marker-defaults
Open

docs(skills): make destructive-test invocation safer by default#41
TheRealAgentK wants to merge 1 commit into
masterfrom
docs/skill-destructive-marker-defaults

Conversation

@TheRealAgentK
Copy link
Copy Markdown
Collaborator

Pytest's -m flag is additive: pytest -m integration matches every test marked integration, including those also marked destructive. The previous skill text presented all three invocations equally, which encouraged PR descriptions and integration READMEs to recommend the bare -m integration form — the dangerous one.

This PR tightens the writing-integration-tests skill in three places:

  1. "When to Use" gets a callout clarifying that the destructive marker is a filter target, not an auto-exclusion
  2. "Running Commands" is reframed so the safe command is the documented default, with a leading warning
  3. New "Documenting How to Run" subsection prescribes PR-description / README conventions (safe command first, no bare -m integration recommendation)
  4. Workflow gets a new step 9 reminding authors to document the commands accordingly

Motivated by review feedback on a Humanitix integration PR (Autohive-AI/autohive-integrations#306) where the marker was applied correctly but the PR description still recommended the bare -m integration invocation.

Pytest's -m flag is additive, so 'pytest -m integration' selects every
test marked 'integration' — including those also marked 'destructive'.
The previous skill text presented all three invocations equally, which
encouraged PR descriptions and READMEs to recommend the bare
'-m integration' form (the dangerous one).

This change:
- Adds a callout in 'When to Use' explaining that the destructive
  marker does NOT auto-exclude tests from -m integration
- Reframes 'Running Commands' so the safe command is the documented
  default, with a leading warning
- Adds a new 'Documenting How to Run' subsection prescribing PR
  description / README conventions
- Appends a step 9 to the workflow checklist for documenting the
  run commands
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 7, 2026

Coverage — 2c756c1 (docs(skills): make destructive-test invocation safer by default) by @TheRealAgentK

Total coverage: 100%

File Stmts Miss Cover Missing
src/autohive_integrations_sdk/__init__.py 2 0 100%
src/autohive_integrations_sdk/integration.py 358 0 100%

@TheRealAgentK TheRealAgentK requested a review from NinosMan May 7, 2026 22:43
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