ship

Security Community

Skill notes

Phase 1: Create PR

Determine the current branch: git branch --show-current Check if a PR already exists: gh pr list --head <branch> --json number,url If no PR exists, create one: Note the PR number.

Phase 2: CI Monitor

Find the latest workflow run: gh run list --branch <branch> --limit 1 --json status,conclusion,databaseId If the run is in progress, watch it: gh run watch <id> If it failed: Get failed logs: gh run view <id> --log-failed Diagnose and fix the issue.

Phase 3: SonarCloud Check

Wait 60 seconds for SonarCloud analysis to propagate. Use get_project_quality_gate_status with project key Brad-Edwards_aptl to check the quality gate. Use search_sonar_issues_in_projects to find new issues on the current branch. If issues found: Fix them.

Phase 4: Code Review

CRITICAL: You MUST use the Skill tool to invoke the built-in review skill. Merge dev into the current branch: git fetch origin dev && git merge origin/dev If there are merge conflicts, resolve them, commit, and push. Call the Skill tool with skill="review" to invoke the real built-in code review. After the review completes, fix ALL issues it identified.

Phase 5: Security Review

CRITICAL: You MUST use the Skill tool to invoke the built-in security-review skill. Call the Skill tool with skill="security-review" to invoke the real built-in security review. After the review completes, fix ALL issues it identified. Same rules as Phase 4: fix everything, defer nothing. After fixing, confirm all findings were addressed.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Create PR

Determine the current branch: `git branch --show-current` Check if a PR already exists: `gh pr list --head <branch> --json number,url` If no PR exists, create one: Note the PR number.

02
Phase 2: CI Monitor

Find the latest workflow run: `gh run list --branch <branch> --limit 1 --json status,conclusion,databaseId` If the run is in progress, watch it: `gh run watch <id>` If it failed: Get failed logs: `gh run view <id> --log-failed` Diagnose and fix the issue.

03
Phase 3: SonarCloud Check

Wait 60 seconds for SonarCloud analysis to propagate. Use `get_project_quality_gate_status` with project key `Brad-Edwards_aptl` to check the quality gate. Use `search_sonar_issues_in_projects` to find new issues on the current branch. If issues found: Fix them.

04
Phase 4: Code Review

CRITICAL: You MUST use the Skill tool to invoke the built-in review skill. Merge dev into the current branch: `git fetch origin dev && git merge origin/dev` If there are merge conflicts, resolve them, commit, and push. Call the Skill tool with `skill="review"` to invoke the real built-in code review. After the review completes, fix ALL issues it identified.

05
Phase 5: Security Review

CRITICAL: You MUST use the Skill tool to invoke the built-in security-review skill. Call the Skill tool with `skill="security-review"` to invoke the real built-in security review. After the review completes, fix ALL issues it identified. Same rules as Phase 4: fix everything, defer nothing. After fixing, confirm all findings were addressed.

06
Phase 6: Final Commit & CI

If ANY fixes were made in Phases 4-5: `git add` all changed files. `git commit -m "Fix code review and security review findings"` `git push` Re-run Phase 2 (CI Monitor).

07
Phase 7: Report (DO NOT MERGE)

You MUST NOT merge the PR. You MUST NOT run `gh pr merge`. The user reviews and merges. Summary of all changes made during the ship process Review findings and what was fixed Security review findings and what was fixed Confirmation: CI green, SonarCloud passed, PR ready for user review

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.