post-release-activities Skill
Systematic activities that need to be performed after a release is done. Published by microsoft in testfx.
Decision snapshot
Is this a fit?
Developers using testfx, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is post-release-activities Skill?
Systematic activities that need to be performed after a release is done. Published by microsoft in testfx. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using testfx
Declared skill metadata
- Source file: .github/skills/post-release-activities/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use post-release-activities Skill
- Use it for developers using testfx.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .github/skills/post-release-activities/SKILL.md
What it does
Systematic activities that need to be performed after a release is done.
Skill instructions
Post-release Activities Skill When to Use This Skill Use this skill when assigned an issue asking you to do the post-release activities. You will be given the branch name for the release. If that information is missing, ask for it and don't proceed with doing anything. Steps to Follow Step 1: Find the release version The branch name only contains the major and minor parts of the version, but not the patch part. To find the full version: 1. Look for eng/Versions.props file in the given branch. 2. Find the value of VersionPrefix. Step 2: Tagging the branch Create a tag for the branch using the version you found in Step 1. The tag name should be v{version} (replace {version} with the version you found in Step 1). After creating the tag, push it to the remote repository. Step 3: Create a GitHub draft release 1. Create a file release-notes.md and add the following content to it: See the release notes here (replace {version} with the version you found in Step 1). 2. Run gh release create v{v
Verified compatibility and discovery
Frequently asked questions
What is post-release-activities?
post-release-activities is a open-source AI agent skill with Copy skill directory. Systematic activities that need to be performed after a release is done.
Who is post-release-activities best for?
post-release-activities is best for reusing agent instructions, scripts, and references.
How do I install post-release-activities?
Install or run post-release-activities using Copy skill directory. Check post-release-activities for the latest setup command.
Is post-release-activities actively maintained?
post-release-activities may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
