verify-and-ship
Skill902 starsChanged 53 days agoApache-2.0View on GitHub
Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Ionate-Technologies/indium-agentkittheir own version, first seen Oct 20, 2026
- Indium-AI-Labs/indium-agentkittheir own version, first seen Oct 11, 2026
- ceedaragents/cyrusword for word, first seen Oct 8, 2026
- Jaeyong-Cho/skillstheir own version, first seen Aug 20, 2026
Other versions4 projects use a version of this.
Word for word · 1
- ceedaragents/cyrus★ 888100% same
Edited · 0
None found.
Wrote their own version · 3
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- Jaeyong-Cho/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- release-core-testSkill
- cyrus-setup-claude-authSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-gitlabSkill
- cyrus-setup-launchSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- cyrus-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
After implementing your changes, follow these steps to verify quality and ship the work.
- Very specific: line 12
Use the issue tracker get_issue tool to fetch the current issue details.
- Distinctive: line 51
Check if the project has changelog files:
- Distinctive: line 56
If changelog files exist, diff against the base branch to detect entries already added by this branch:
- Distinctive: line 65
If the diff shows this branch already added a changelog entry for the current issue (matching the issue identifier), update that entry …
- Distinctive: line 66
If the diff shows this branch added changelog entries for a different issue or no entries at all, add a new entry.
- Very specific: line 69
Place entries under ## [Unreleased] in the appropriate subsection (### Added, ### Changed, ### Fixed, ### Removed)
- Distinctive: line 72
Follow Keep a Changelog format
- Distinctive: line 77
Commit with clear, descriptive messages following the project's commit conventions
- Distinctive: line 100
Update the PR/MR with a comprehensive description:
- Very specific: line 101
Assignee attribution: If <github_username> is available in the assignee context, add Assignee: @username (Display Name) at the top of the …
- Very specific: line 105
Interaction tip: Add this at the end (before the marker), using the bot username from <github_bot_username> or <gitlab_bot_username> in the …
- Very specific: line 111
Remove any "WIP:" or "Draft:" prefix from the title.
- Very specific: line 113
Verify the PR/MR targets the correct base branch from <base_branch> in the issue context.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify and Ship
After implementing your changes, follow these steps to verify quality and ship the work.
1. Acceptance Criteria Validation (CRITICAL)
Use the issue tracker get_issue tool to fetch the current issue details. Extract ALL acceptance criteria from the issue description and verify each one is satisfied by the implementation. If no explicit criteria exist, validate against the implied requirements from the issue title and description.
2. Quality Checks
Choose validation by changed behavior, risk, and existing coverage. Verification is required; new automated tests and a full-suite run are not required for every change. Follow repository-specific checks and CI gates where applicable.
- Direct verification — For routine release scripts, packaging/build metadata, CI, documentation, and instruction edits, prefer syntax checks, a safe dry run, artifact inspection, an isolated install smoke check, or a consistency review when those are sufficient. Record the command/result or review performed in the PR; no new test file or validation report is needed merely to show work.
- Automated tests — Run relevant existing tests. Add or retain a regression test only when it catches a concrete consequential failure and its protection justifies its maintenance. Examples include publishing the wrong artifact, unintentionally moving stable tags, or accepting invalid release evidence. Explain the failure each new test catches. Do not add brittle assertions on documentation wording or source text, tests that mirror implementation, or elaborate scaffolding for low-risk edits. A script filename alone neither requires tests nor exempts consequential behavior from protection.
- Scope — Broaden testing when shared behavior, failures, or unresolved risk warrants it; do not automatically run the full suite or generate coverage reports. Once sufficient checks pass, stop repeating them unless changes or new evidence justify another run. Investigate relevant failures rather than retrying unchanged commands. Report any unresolved failures honestly.
- Lint, types, build — Run checks relevant to the changed files and required repository gates. Fix introduced failures.
- Review — Check correctness, scope, and maintainability, including whether proposed tests provide useful protection.
Where the repository uses F1, apply its canonical
skills/f1-test-drive/SKILL.md applicability policy before invoking a drive or
requesting evidence. Nonapplicable changes need proportionate checks and a brief
PR note, without an F1 run or report. Do not infer an F1 requirement from this
skill. Preserve existing safeguards for consequential failures.
3. Changelog Update
Check if the project has changelog files:
ls -la CHANGELOG.md CHANGELOG.internal.md 2>/dev/null || echo "NO_CHANGELOG"If changelog files exist, diff against the base branch to detect entries already added by this branch:
# See what changelog lines this branch has added compared to the base branch
# Replace <base_branch> with the actual base branch from the issue context
git diff <base_branch> -- CHANGELOG.md CHANGELOG.internal.md 2>/dev/nullHandling existing entries:
- If the diff shows this branch already added a changelog entry for the current issue (matching the issue identifier), update that entry in-place (e.g., to add the PR/MR link or refine the description). Do NOT add a duplicate entry.
- If the diff shows this branch added changelog entries for a different issue or no entries at all, add a new entry.
Adding or updating entries:
- Place entries under
## [Unreleased]in the appropriate subsection (### Added,### Changed,### Fixed,### Removed) - Focus on end-user impact — be concise but descriptive
- Include the Linear issue identifier and PR/MR link (format:
([ISSUE-ID](linear_url), [#NUMBER](PR_OR_MR_URL))) - Follow Keep a Changelog format
4. Commit and Push
- Stage all relevant changes (including changelog updates)
- Commit with clear, descriptive messages following the project's commit conventions
- Push to the remote repository
5. Create or Update PR/MR
Determine the platform from the repository context (<github_url> or <gitlab_url> in the issue context). Use the appropriate tool for the platform.
GitHub (when <github_url> is present)
git push -u origin HEAD
gh pr view --json url,number 2>/dev/null || gh pr create --draft --base [base_branch from context] --title "[descriptive title]" --body "Work in progress"GitLab (when <gitlab_url> is present)
git push -u origin HEAD
glab mr view 2>/dev/null || glab mr create --draft --target-branch [base_branch from context] --title "[descriptive title]" --description "Work in progress"PR/MR Description
Update the PR/MR with a comprehensive description:
- Assignee attribution: If
<github_username>is available in the assignee context, addAssignee: @username ([Display Name](linear_profile_url))at the top of the body. If only a linear profile URL is available, useAssignee: [Display Name](linear_profile_url). - Summary of changes, implementation approach, and testing performed
- Link to the Linear issue
- Cyrus marker: Include
<!-- generated-by-cyrus -->as a hidden HTML comment at the end of the body - Interaction tip: Add this at the end (before the marker), using the bot username from
<github_bot_username>or<gitlab_bot_username>in the<agent_context>block of the system prompt. If<agent_context>is not present, default tocyrusagent:--- > **Tip:** I will respond to comments that @ mention @<bot_username> on this PR/MR. You can also submit a review with all your feedback at once, and I will automatically wake up to address each comment.
Remove any "WIP:" or "Draft:" prefix from the title. Check <agent_guidance> — only mark the PR/MR as ready if guidance does NOT specify keeping them as drafts.
Verify the PR/MR targets the correct base branch from <base_branch> in the issue context.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

